DK EHMI Endpoint Register (EER)
2.0.1-draft - ci-build
DK EHMI Endpoint Register (EER)
2.0.1-draft - ci-build
DK EHMI Endpoint Register (EER), published by MedCom. This guide is not an authorized publication; it is the continuous build for version 2.0.1-draft built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-ehmi-eer/ and changes regularly. See the Directory of published versions
<Endpoint xmlns="http://hl7.org/fhir">
<id value="LaegerneStjernepladsen.SOR.5790002401428"/>
<meta>
<profile
value="http://medcomehmi.dk/ig/eer/StructureDefinition/eer.dk.sor.endpoint"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Endpoint LaegerneStjernepladsen.SOR.5790002401428</b></p><a name="LaegerneStjernepladsen.SOR.5790002401428"> </a><a name="hcLaegerneStjernepladsen.SOR.5790002401428"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px"/><p style="margin-bottom: 0px">Profile: <a href="StructureDefinition-eer.dk.sor.endpoint.html">EerSOREndpoint</a></p></div><p><b>EER System Extension - AP</b>: <a href="Device-EerDeviceAP-MultiMedAP.html">Device: identifier = EerDeviceAP-MultiMedAP; status = active; manufacturer = MultiMed; type = eDelivery Access Point</a></p><p><b>identifier</b>: <a href="http://terminology.hl7.org/6.3.0/NamingSystem-GLN.html" title="Global Location Number (GLN) can be used by companies to identify their locations, giving them complete flexibility to identify any type or level of location required.
For more information as to how GLNs are used in healthcare, see a GS1 provided guide located here https://www.gs1.org/docs/healthcare/GLN_Healthcare_Imp_Guide.pdf
For additional information regarding the GLN standard refer to the GS1 General Specifications (https://www.gs1.org/standards/barcodes-epcrfid-id-keys/gs1-general-specifications) and for assignment refer to the GS1 GLN Allocation Rules (https://www.gs1.org/1/glnrules/en/).
GS1 local offices handle all enquiries related to GS1 standards. Please see the list of GS1 offices (https://www.gs1.org/contact/overview) for more information.
In relation to the "Healthcare GLN Implementation Guideline":
"GS1®, under its IP Policy, seeks to avoid uncertainty regarding intellectual property claims by requiring the participants in the Work Group that developed this Healthcare GLN Implementation Guideline to agree to grant to GS1 members a royalty-free licence or a RAND licence to Necessary Claims, as that term is defined in the GS1 IP Policy. Furthermore, attention is drawn to the possibility that an implementation of one or more features of this Specification may be the subject of a patent or other intellectual property right that does not involve a Necessary Claim. Any such patent or other intellectual property right is not subject to the licensing obligations of GS1. Moreover, the agreement to grant licences provided under the GS1 IP Policy does not include IP rights and any claims of third parties who were not participants in the Work Group.
Accordingly, GS1 recommends that any organisation developing an implementation designed to be in conformance with this Specification should determine whether there are any patents that may encompass a specific implementation that the organisation is developing in compliance with the Specification and whether a licence under a patent or other intellectual property right is needed. Such a determination of a need for licencing should be made in view of the details of the specific system designed by the organisation in consultation with their own patent counsel."
"GS1 disclaims all liability for any damages arising from use or misuse of this document, whether special, indirect, consequential, or compensatory damages, and including liability for infringement of any intellectual property rights, relating to use of information in or reliance upon this document."
GS1 and the GS1 logo are registered trademarks of GS1 AISBL.">Global Location Number (GLN)</a>/5790002401428</p><p><b>status</b>: Active</p><p><b>connectionType</b>: <a href="https://build.fhir.org/ig/medcomdk/dk-ehmi-terminology/CodeSystem-eer-endpoint-connection-type.html#eer-endpoint-connection-type-EerMessagingEdelivery">EHMI Endpoint Register (EER) - Connection Types CS: EerMessagingEdelivery</a> (EHMI messaging via eDelivery)</p><p><b>name</b>: EER SOR Endpoint - LaegerneStjernepladsen.SOR.5790002401428 FHIR Endpoint</p><p><b>managingOrganization</b>: <a href="Organization-LaegerneStjernepladsen.SOR.698131000016001.html">Organization Lægerne Stjernepladsen I/S</a></p><p><b>period</b>: 2025-01-01 --> (ongoing)</p><p><b>payloadType</b>: <span title="Codes:{http://medcomehmi.dk/ig/terminology/CodeSystem/ehmi-message-definition-uri urn:dk:healthcare:medcom:messaging:fhir:structuredefinition::homecareobservation-message##urn:dk:medcom:fhir:homecareobservation-message::1.2}">HomeCareObservation 1.2</span>, <span title="Codes:{http://medcomehmi.dk/ig/terminology/CodeSystem/ehmi-message-definition-uri urn:dk:healthcare:medcom:messaging:fhir:structuredefinition::acknowledgement-message##urn:dk:medcom:fhir:acknowledgement-message::2.0}">Acknowledgement 2.0</span>, <span title="Codes:{http://medcomehmi.dk/ig/terminology/CodeSystem/ehmi-message-definition-uri urn:dk:healthcare:messaging:oasis:ebxml:schema:xsd::ehmisbdh-acknowledgement##urn:dk:ehmi:sbdh:ehmisbdh-acknowledgement::1.0}">ehmiSBDH Acknowledgement 1.0</span></p><p><b>payloadMimeType</b>: text/xml, application/fhir+xml, application/fhir+json</p><p><b>address</b>: <a href="https://example.org/fhir">https://example.org/fhir</a></p></div>
</text>
<extension
url="http://medcomehmi.dk/ig/eer/StructureDefinition/eer-dk-ap-system-extension">
<valueReference>🔗
<reference value="Device/EerDeviceAP-MultiMedAP"/>
</valueReference>
</extension>
<identifier>
<system value="http://www.gs1.org/gln"/>
<value value="5790002401428"/>
</identifier>
<status value="active"/>
<connectionType>
<system
value="http://medcomehmi.dk/ig/terminology/CodeSystem/eer-endpoint-connection-type"/>
<code value="EerMessagingEdelivery"/>
</connectionType>
<name
value="EER SOR Endpoint - LaegerneStjernepladsen.SOR.5790002401428 FHIR Endpoint"/>
<managingOrganization>🔗
<reference
value="Organization/LaegerneStjernepladsen.SOR.698131000016001"/>
</managingOrganization>
<period>
<start value="2025-01-01"/>
</period>
<payloadType>
<coding>
<system
value="http://medcomehmi.dk/ig/terminology/CodeSystem/ehmi-message-definition-uri"/>
<code
value="urn:dk:healthcare:medcom:messaging:fhir:structuredefinition::homecareobservation-message##urn:dk:medcom:fhir:homecareobservation-message::1.2"/>
</coding>
</payloadType>
<payloadType>
<coding>
<system
value="http://medcomehmi.dk/ig/terminology/CodeSystem/ehmi-message-definition-uri"/>
<code
value="urn:dk:healthcare:medcom:messaging:fhir:structuredefinition::acknowledgement-message##urn:dk:medcom:fhir:acknowledgement-message::2.0"/>
</coding>
</payloadType>
<payloadType>
<coding>
<system
value="http://medcomehmi.dk/ig/terminology/CodeSystem/ehmi-message-definition-uri"/>
<code
value="urn:dk:healthcare:messaging:oasis:ebxml:schema:xsd::ehmisbdh-acknowledgement##urn:dk:ehmi:sbdh:ehmisbdh-acknowledgement::1.0"/>
</coding>
</payloadType>
<payloadMimeType value="text/xml"/>
<payloadMimeType value="application/fhir+xml"/>
<payloadMimeType value="application/fhir+json"/>
<address value="https://example.org/fhir"/>
</Endpoint>