National Electronic Health Record Implementation Guide
0.1.0 - ci-build
National Electronic Health Record Implementation Guide
0.1.0 - ci-build
National Electronic Health Record Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Connecting systems SHALL use standard FHIR Restful create and update interactions.
E.g.
POST [base]/[resource]
PUT [base]/[resource]/[id]
This is modeled as a FHIR Document and users SHALL use this interface to send clinical data at discharge to the NEHR. All Resources are sent in a Bundle of type document with a Composition Resource as the first entry, Patient second, and other Resources, referenced by the Composition, in the following Bundle entries. See this page for more details.
POST [base]/Bundle
The LKDischargeSummary and LKDischargeSummaryBundle profiles have been designed for this use case.
This is modeled with a Composition Resource, each section referencing instances of FHIR Resources. As specified by Sri Lanka, this is not a formal document (CDA or FHIR Document) and does not use a Bundle, but a simple list referencing Resource instances that already exist in the NEHR. Users SHALL use the following to submit an Encounter Summary:
POST [base]/Composition
The LKEncounterSummary profiles have been designed for this use case.
Consideration 🔎 The initial implementation may not have all the registries online, as such FHIR References to Organizations, Locations, Practitioners or HeathcareServices may not have an absolute or relative URL pointing to an accessible FHIR Resource instance. These Resources should use the display or identifier elements as alternatives for the Resource Reference.
Consideration 🔎 This is somewhat complicated as individuals may have multiple PHNs and thus the longitudinal record for a patient may be related to several Patient Resource instances in the NEHR. Depending on the nature of the business requirement, requesting clinical data from the NEHR may involve several calls, one per PHN.
Standard queries, using id, identifiers or search parameters are supported and SHALL be used to read NEHR FHIR Resources.
GET [base]/[resource]?[search_parameters]
GET [base]/[resource]/[id]
Intial support for read and serach interactions SHALL include Patient, Encounter, Condition, AllergyIntolerance, Procedure, MedicationRequest, MedicationAdministration, MedicationDispense, MedicationStatement, Immunization, Observation, ServiceRequest, CarePlan, and DiagnosticReport.
Improvement 🔎 As requirements for consumption of the NEHR clinical data are refined so will the read interactions.
The vread interaction SHALL be supported for Resources (listed in the above read/search section).
For example
GET [base]/Encounter/123/_history/3