DK MedCom Core
2.4.0 - release
DK MedCom Core
2.4.0 - release
This page is part of the DK MedCom Core (v2.4.0: Release) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.3.0. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define constraints on FHIR resources for systems conforming to this implementation guide.
| MedComCoreCareTeam |
Careteam participating in the care of a patient |
| MedComCoreDiagnosticReport |
Report containing all observation results. |
| MedComCoreEncounter |
An interaction between a patient/citizen and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient/citizen. |
| MedComCoreObservation |
Observation profile intended to be used in MedComHomeCareObservation and MedCom’s Laboratory standards. |
| MedComCoreOrganization |
A formally recognized organizations within danish healthcare, registered with a SOR identifier issued by The Danish Health Data Authority |
| MedComCorePatient |
Patient/citizen resource to use as subject in MedCom communication. |
| MedComCorePractitioner |
Practitioner resource is used to describe a healthcare professional or another actor involved in citizen or patient care. |
| MedComCorePractitionerRole |
PractitionerRole resource used to describe the role of a healthcare professional or another actor involved in citizen or patient care. |
| MedComMedia |
Profile to capture relevant images,audio, video and document as part of the healthcare process |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| AssignedIdentifier |
An UUID identifier assigned by an organisation |
| LPR3 Identifier |
Identifier holding a LPR3 identifier |
| MedComMessagingContactPoint |
The datatype ContactPoint is specified for use in MedCom messages. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| ContactExtension |
Extension that contains the contact information |
| DateTimeExtension |
Date and time of this payload |
| IdentifierExtension |
An extension holding a specific identifier datatype |
| PractitionerExtension |
Reference to a PractitionerRole and subsequent Practitioner |
| SenderExtension |
Reference to a more specfic sender of a message. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Aros Burn Center |
An organization with a SOR identifier and name. |
| Birgit Berggren |
Patient described with minimal information and replacement cpr-number. Valid only if used in a Bundle. |
| Brita Test Berggren |
Patient described with maximum information. Valid only if used in a Bundle. |
| Bruno Test Elmer |
Patient described with minimal information. Valid only if used in a Bundle. |
| Cæcar Test Østergård |
Deceased patient described with maximum information. Valid only if used in a Bundle. |
| Example of a Practitioner |
Example of a practitioner with a name |
| Example of a PractitionerRole |
Example of a practitioner role with a code and reference to a practitioner |
| Example of a careteam |
Example of a careteam with a name and a reference to an organization |
| MedCom Core Encounter |
Example of a simple MedCom Core Encounter |
| Normal EKG |
An example of an EKG that can be sendt with an diagnostic repport |
| Practitioner Clinic |
An organization with a SOR identifier, without name. |
| PractitionerRole with a role and reference to a practitioner |
PractitionerRole with a role and reference to a practitioner |