Document Repository Implementation Guide
0.1.0 - ci-build Sri Lanka flag

Document Repository Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Sri Lanka Document Repository

Official URL: http://ig.hiu.lk/fhir/documentrepository/ImplementationGuide/fhir.lk.documentrepository Version: 0.1.0
Draft as of 2025-10-23 Computable Name: Sri_Lanka_Document_Repository_ImplemenationGuide

The role of documents within a health enterprise is important as they provide holistic, validated, and complete representations of an event as the originating provider documented it. Clinical documents are a useful documentation pattern for:

  • Recording prescription requests which are to be filled by a pharmacy not located within the prescribing facility.
  • Recording the fulfillment (dispense) of prescriptions from public or private pharmacies including substitutions (i.e., generics or alternate dosing)
  • Managing repeating, long-term prescriptions (standing orders)
  • Summarising encounters or visits by an institution (examples: discharge summaries, visit summaries)
  • Summarising or providing rationale for a diagnosis or condition (example: diagnostic note)
  • Summarising information between modalities (example: radiology report based on ultrasound capture)
  • Representing signed, stand-alone medically legal documentation from a provider which cannot be altered, transformed, or changed (although, derivative information can be extracted, the original document cannot be changed)

This guide describes the interfaces used by the Sri Lanka Document Repository.

Some conventions are defined below, an overview is provided which describes some of the design decisions and data structures used for the Document Repository. A detailed specification follows interface descriptions.

This guide is part of a suite of guides that build on one another so that complex Message exchanges can be designed and useful Resource profiles created in the advanced guides.

Base Guides
FHIR R4

Foundational Guides
Client Registry
Provider Registry
Facility Registry

Advanced Guides
Document Repository
National Electronic Health Record Repository
Electronic Referrals

Data Absent Reason

Use of data absent reason extension SHALL be permitted on mandatory elements. As scenarios arise, and experience is gained, this will be refined.

Must Support

The Producer (sender) SHALL populate if known and allowed. The Consumer (receiver) SHALL process (store and return in response). Both of these obligations use the term allowed which is referencing the data masking section just below.

Data Masking

Using the data absent reason extension to mask data SHALL be permitted. As scenarios arise, and experience is gained, this will be refined.

Synchronous Interfaces

All interfaces are synchronous.

🔎 At times when the network is unreliable the responsibility to retry and queue messages lies with the connecting system.

The Document Repository will follow Sir Lanka's policies on protecting client demographic information; allowing only authorized systems and individuals access. Those polices described at a high level in the Digital Health Blueprint document, section "2.5.5 Security and Privacy by Design" and section "4.2.7 Security & Privacy". See also the "National eHealth Guidelines and Standards" (version 2.0) document.

The specification of security, privacy and consent is beyond the scope of this guide.

Conformance and Conformance Language

Unless otherwise specified base FHIR R4 conformance standards are assumed by this guide.

This guide follows standard FHIR R4 definitions for conformance language. Follow this link for more details.

Licensing

This guide is licensed under the CC0-1.0 license.