This specification conforms to FHIR®© R4
MedCom Shared Notes
Table of Content
This page presents MedCom’s Shared Notes standard (Danish: Deling af journalnotater). The purpose of the standard is to enable the secure and structured sharing of notes (Da: journalnotater) initially from general practitioners’ systems (LPS). The Shared Notes standard supports the exchange of personally identifiable health information and ensures that notes can be accessed consistently and safely across sectors. The standard contributes to better care coordination and continuity by giving authorized healthcare professionals access to up-to-date documentation from other healthcare professionals.
The Notes standard is implemented as a FHIR Document and shared over the National Service Platform (NSP) in Denmark. A simple illustration of the flow of data is depicted in Figure 1. A short description of the flow follows:
- The general practitioner documents the consultation by authoring a note, which may include relevant assessments, observations, and decisions.
- The note is made available for sharing through the national healthcare infrastructure in accordance with applicable authorization and access rules.
- Another healthcare professional with the appropriate authorization requests access to the shared note.
- A document containing the journal note is retrieved and made available, allowing the healthcare professional to review the clinical documentation from the consultation.
1 Standard Documentation
On the project page for Shared notes on NSPOP, the following documentation can be found:
- Overall purpose of the standard
- Logical information and data models
- Business rules
- Technical guide for implementation of the Shared Notes standard.
On this page, provided by MedCom, additional information on how to implement the standard Shared Notes:
- User stories
- Use cases
- Technical specifications in terms of the relevant Implementation Guide (IG).
- Mapping from logical data model to Shared Notes
- Material for test and certification
1.1 User Stories
A user story is an informal, general description of a systems functionality as perceived from the user’s perspective. User stories have the end user at the centre of the dialogue about system functionality. User stories describe which needs the end user wants fulfilled, so that the developer understands the context of the development task: why they are developing the function and what value it must provide the end user. Not all user stories will be supported with this current implementation, which is noted for the specific user story.
1.2 Use Cases
Use cases describe the different scenarios a standard support. For a certain real-world scenario, it describes the requirements for the content of a document. The purpose of the use cases is to ensure a coherent implementation and use of the Shared Notes standard. The descriptions are targeted IT-system vendors and the people responsible for the implementation.
1.3 Technical specification
The technical specification for the Shared Notes standard is composed by profiles from two IGs.
- MedCom Document, which provides the overall document structure and base requirements
- MedCom Shared Notes, which provides the requirements specific for the use of the Shared Notes standard.
1.4 Mapping from logical data model to Notes
The follwoing page is intended to help translate the logical data model to the FHIR Notes standard. More information about the mapping can be found on the following page.
2 Test and Certification
Certification of a system implies both an approved testprotocol and run-through of test scripts in ITB (Interoperability Test Bed). ITB describes an infrastructure that allows for automated test and validation against the IG’s developed by MedCom.
Click here to find the description of test and certification of FHIR standards in MedCom..
Providing a Notes document
- Testprotocol
- ITB Testscripts
Retrieving a Notes document
- Testprotocol
About
Support or contact
MedCom is responsible for this page. If you have any questions regarding this page, please contact fhir@medcom.dk or write to MedCom's stream on Zulip.Version of this documentation
The version of this documentation is: Version x.y.z-alpha.1 You can find the release note of the version here"FHIR® is the registered trademark of HL7 and is used with the permission of HL7. Use of the FHIR trademark does not constitute endorsement of this implementation guide by HL7, nor affirmation that this content is conformant to the various applicable standards"