|
Type
|
Reference
|
Content
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=52581000016005
|
|
web
|
sor2.sum.dsdn.dk
|
https://sor2.sum.dsdn.dk/#id=1144561000016002
|
|
web
|
tel:+4505577668
|
telecom
: +45 05577668
|
|
web
|
www.medcom.dk
|
|
|
web
|
github.com
|
MedCom HomeCareObservation, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 1.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk_HomeCareObservations/
and changes regularly. See the Directory of published versions
|
|
web
|
www.medcom.dk
|
IG © 2023+ MedCom
. Package medcom.fhir.dk.homecareobservation#1.1.0 based on FHIR 4.0.1
. Generated 2025-04-09
Links: Table of Contents |
QA Report
| Accessibility statement (Tilgængelighedserklæring)
|
|
web
|
www.was.digst.dk
|
Links: Table of Contents
|
QA Report
| Accessibility statement (Tilgængelighedserklæring)
|
|
web
|
medcomfhir.dk
|
Name: of the person responsible for producing the report. The name shall be described using a MedComCorePractitioner
.
|
|
web
|
medcomfhir.dk
|
Author role: The role (Danish: stillingsbetegnelse) of the person producing the report shall be described using a MedComCorePractitionerRole
|
|
web
|
medcomfhir.dk
|
In MedComHomeCareDiagnosticReport it is allowed to include attachments. When including an attachment to a HomeCareDiagnosticReport then the element DiagnosticReport.media.link shall be used. The DiagnosticReport.media.link reference to MedComCoreMedia resource where the atachment shall be added.
It is up to the user to assess when it is relevant to send an attachment.
Only an attachment of the permitted formats must be included.
Click here to see the permitted formats of an attachment
|
|
web
|
en.wikipedia.org
|
Both Bundle.link and Bundle.entry.link are defined to support providing additional context when Bundles are used (e.g. HATEOAS
).
|
|
web
|
medcomdk.github.io
|
More information about the clinical guidelines for applications can be found here.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationMessage
is a constraint of the MedComMessagingMessage
further to use the MedComHomeCareObservationsMessageHeader
and to require exactly one MedComCorePatient
.
Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComHomeCareObservationMessageAcitivityCodes
ValueSet, which contains activities such as new-message, forward-message, and other activities triggering the message.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationMessage
is a constraint of the MedComMessagingMessage
further to use the MedComHomeCareObservationsMessageHeader
and to require exactly one MedComCorePatient
.
Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComHomeCareObservationMessageAcitivityCodes
ValueSet, which contains activities such as new-message, forward-message, and other activities triggering the message.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationMessage
is a constraint of the MedComMessagingMessage
further to use the MedComHomeCareObservationsMessageHeader
and to require exactly one MedComCorePatient
.
Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComHomeCareObservationMessageAcitivityCodes
ValueSet, which contains activities such as new-message, forward-message, and other activities triggering the message.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationMessage
is a constraint of the MedComMessagingMessage
further to use the MedComHomeCareObservationsMessageHeader
and to require exactly one MedComCorePatient
.
Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComHomeCareObservationMessageAcitivityCodes
ValueSet, which contains activities such as new-message, forward-message, and other activities triggering the message.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationMessage
is a constraint of the MedComMessagingMessage
further to use the MedComHomeCareObservationsMessageHeader
and to require exactly one MedComCorePatient
.
Furthermore, it contains rules that constrains the ValueSet of activities in the MedComMessagingProvenance
profile to only contain activities from the MedComHomeCareObservationMessageAcitivityCodes
ValueSet, which contains activities such as new-message, forward-message, and other activities triggering the message.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationsMessageHeader
constrains the MedComMessagingMessageHeader
further to specify the fixed coding for this message and constrains the use of carbon-copy destination.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservationsMessageHeader
constrains the MedComMessagingMessageHeader
further to specify the fixed coding for this message and constrains the use of carbon-copy destination.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareDiagnosticReport
profile contains the main content of the HomeCareObservation message. It is inherited from the profile MedComCoreDiagnosticReport
. The MedComHomeCareDiagnosticReport shall include observation results performed and produced by the municipalties acute care team. Futher shall the MedComHomeCareDiagnostiscRepport include an information about the status of the observation results.
The profile also includes information about the performer, i.e the person who performed and produced observations results. The perfomer informations consist of a signature that requires the name, title and relevant telephone number.Further, this profile also contains the clinical observations (nursing assessments) regarding the citizens overall results and health status.
Click here for read more information about the clinical observations.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareDiagnosticReport
profile contains the main content of the HomeCareObservation message. It is inherited from the profile MedComCoreDiagnosticReport
. The MedComHomeCareDiagnosticReport shall include observation results performed and produced by the municipalties acute care team. Futher shall the MedComHomeCareDiagnostiscRepport include an information about the status of the observation results.
The profile also includes information about the performer, i.e the person who performed and produced observations results. The perfomer informations consist of a signature that requires the name, title and relevant telephone number.Further, this profile also contains the clinical observations (nursing assessments) regarding the citizens overall results and health status.
Click here for read more information about the clinical observations.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservation
profile inherits from the MedComCoreObservation profile. This profile includes infromation about what observation was performed, what date & time, by whom, and what result was obtained.
Too expres what observation was performed a Observation.code.coding elemen shall be used. In HomeCareObservation it is allowed to ude NPU codes for observations and MedCom (MCS) codes for observations.
Click here to see the ValueSet for NPU codes.
|
|
web
|
medcomfhir.dk
|
The MedComHomeCareObservation
profile inherits from the MedComCoreObservation profile. This profile includes infromation about what observation was performed, what date & time, by whom, and what result was obtained.
Too expres what observation was performed a Observation.code.coding elemen shall be used. In HomeCareObservation it is allowed to ude NPU codes for observations and MedCom (MCS) codes for observations.
Click here to see the ValueSet for NPU codes.
|
|
web
|
medcomfhir.dk
|
Click here to see the ValueSet for MCS codes.
|
|
web
|
medcomfhir.dk
|
The MedComProducerOrganization
profile is used in a HomeCareObservation message to represent the organization that is responsible for performing and analysing, thereby producing, the observation results e.g. acute careteam. The MedComProducerOrganization shall be identified using municipality SOR-ID, and a producer-ID. The producer-ID consists of a three letter code, which is displayed on the terminology IG
. In a receiver system, the interpretation of the two codes will together state that an acute care team from e.g. Aarhus municipality is the producer of the results.
|
|
web
|
medcomfhir.dk
|
The MedComCoreMedia
profile is used in HomeCareObservation message to represents the relevant attachements added to the HomeCareDagnosticReport. MedComCoreMedia is referred from HomCareDiagnosticReport.media.link.
|
|
web
|
medcomfhir.dk
|
The HomeCareObservation message includes several timestamps. These timestamps are present in the profiles MedComHomeCareDiagnosticReport
, MedComHomeCareObservation
, MedComHomeCareObservationMessage
, and MedComMessagingProvenance
and have different purposes:
|
|
web
|
medcomfhir.dk
|
The HomeCareObservation message includes several timestamps. These timestamps are present in the profiles MedComHomeCareDiagnosticReport
, MedComHomeCareObservation
, MedComHomeCareObservationMessage
, and MedComMessagingProvenance
and have different purposes:
|
|
web
|
medcomfhir.dk
|
The HomeCareObservation message includes several timestamps. These timestamps are present in the profiles MedComHomeCareDiagnosticReport
, MedComHomeCareObservation
, MedComHomeCareObservationMessage
, and MedComMessagingProvenance
and have different purposes:
|
|
web
|
medcomfhir.dk
|
The sender of the HomeCareObservation Message shall be able to cancel the already sent HomeCareObservation Message if the message has been sent on an incorrect civil registration number, if the receiver is incorrect or if the content in an attachment is concerning an incorrect civic registration number. If the sender cancel the already sent HomeCareObservation Message then the cancellation applies to whole message and not only to the wrong observation result.
If the user wants to cancel the message, then the reason of cancellation shall be written in the clinical comment. Alternatively, the user can also add one of MedCom's predefined cancellation reason phrases that should be added to the clinical comment.
Click here to read MedCom's predefined phrases.
. The cancellation reason shall be added to the DiagnosticRepport.conclusion element.
|
|
web
|
hl7.dk
|
This IG has a dependency to the MedCom Core IG
, MedCom Messaging IG
, MedCom Terminology IG
and DK-core v. 2.0.0
, where the latter is defined by HL7 Denmark
. These dependencies are currently reflected in MedComHomeCareMessage, and MedComHomeMessageHeader which both inherits from profiles defined MedComMessaging IG. Further, it is reflected in references to MedComCorePatient, MedComCoreEncounter, MedComCoreOrganization and MedComMessagingOrganization.
|
|
web
|
medcomfhir.dk
|
Content in this IG can be downloaded in npm format under Download
. This can be used to validate locale FHIR profiles against.
|
|
web
|
medcomdk.github.io
|
On the introduction page for HomeCareObservations
the following documentation can be found:
|
|
web
|
www.medcom.dk
|
MedCom
is responsible for this IG.
|
|
web
|
www.was.digst.dk
|
tilgængelighedserklæring
|
