Integration using existing storage solution
EHR-systems that support direct integration through an XDS/XCA API-interface for sharing documents, can utilize these to integrate as a document source.
The primary protocol is SOAP-based communication using the IHE XDS profile.
For documentation on the XDS Metadata format
- Abstract Metadata Model - IHE ITI TF Vol3
- ebRIM Representation - IHE ITI TF Vol3
- Norwegian profile for XDS metadata
Transactions
Slack-channel for integration questions
When integrating with Norsk helsenetts storage solution, you need to be assigned an instance of XcaDocumentSource.
You will get an Object Identifier identifying your instance of XcaDocumentSource. When uploading documents, this identifier must be included in the relevant properties of the FHIR-bundle.
To get an instance of XcaDocumentSource, and for any questions regarding integrations, feel free to contact us in our Slack-channel:
#ext-nhn-pasientens-journaldokumenter
Steps when integrating with existing Storage Solution
As an integrator, you will need an integration layer between your Storage Solution, that can communicate with NHNs XCA Initiating gateway
- The integration layer must accept both ITI-38 and ITI-39 (multipart) requests, and correctly formatted responses.
- The integration layer must handle business logic related to ConfidentialityCodes for citizen and healthcare personell.
- The integration layer must handle access control i.a. PurposeOfUse, HCP Role, HPR number, Organization etc.
Existing Storage Solution integrated with NHN
flowchart LR
act[Healthcare <br>personell]
subgraph "EPR system"
eepr[EPR system]
epdb[(Storage Solution)]
xdslr[[XDS/XCA<br>Integration<br>layer]]
end
usr(("End user<br>(Helsenorge or<br> Kjernejournal)"))
subgraph "NHN"
nhn[NHN XCA Initiating Gateway]
end
act --Uploads documents--> eepr --Uploads to<br>internal storage--> epdb
usr --Wants to<br>retrieve<br>documents--> nhn <--ITI-38/ITI-39--> xdslr --> epdb
Existing storage, documents being uploaded by the EPR, and the XDS/XCA Integration Layer handling ITI-38 and ITI-39 requests