Unattributed Code Systems

Copyright Fragment

This fragment is available on xhtml-fragments.html

This publication includes IP covered under the following statements.

Copyright and Registered Trademark Uses

External References

Type Reference Content
web eDeliveryAccessPoint.aar.dk address : http://eDeliveryAccessPoint.aar.dk/fhir
web edelivery.endpoint.aar.dk address : http://edelivery.endpoint.aar.dk/fhir/5790000123117
web www.eDeliveryAccessPoint.dk address : http://www.eDeliveryAccessPoint.dk/fhir
web example.org address : https://example.org/fhir
web tel:+123456789 telecom : +123456789 , info@example.org
web medcomdk.github.io
web medcom.dk IG © 2025+ MedCom . Package dk.ehmi.eer#1.0.0-draft based on FHIR 4.0.1 . Generated 2025-09-10
Links: Table of Contents | QA Report | This IG is part of the EHMI universe. EHMI Main site | Accessibility statement (Tilgængelighedserklæring)
web ehmi.dk Links: Table of Contents | QA Report | This IG is part of the EHMI universe. EHMI Main site | Accessibility statement (Tilgængelighedserklæring)
web www.was.digst.dk Links: Table of Contents | QA Report | This IG is part of the EHMI universe. EHMI Main site | Accessibility statement (Tilgængelighedserklæring)
web profiles.ihe.net A Care Services Selective Supplier shall support responding to a request for both the JSON and the XML messaging formats as defined in FHIR. A Care Services Selective Consumer shall accept either the JSON or the XML messaging formats as defined in FHIR. See ITI TF-2: Z.6 for more details.
web profiles.ihe.net See ITI TF-2: Appendix W for informative implementation material for this transaction.
web profiles.ihe.net See ITI TF-2: Appendix Z.6 for more details on response format handling. See ITI TF-2: Appendix Z.7 for guidance on Access Denied.
web profiles.ihe.net See ITI TF-2: Appendix Z.6 for more details on response format handling. See ITI TF-2: Appendix Z.7 for guidance on Access Denied.
web profiles.ihe.net See ITI TF-2: Appendix Z.8 for common mobile security considerations.
web profiles.ihe.net They shall also support the requirements in ITI TF-2: Z.6 , Populating the Expected Response Format.
web www.google.com Search this IG
web profiles.ihe.net IHE uses the normative words: Shall, Should, and May according to standards conventions .
web profiles.ihe.net mCSD uses Must Support in StructureDefinition profiles. This is equivalent to the IHE use of R2 as defined in Appendix Z .
web github.com The source code for this Implementation Guide can be found on IHE GitHub . <!–
web www.iso.org ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage
web profiles.ihe.net Use cases and solutions using mCSD are outlined in the mCSD White Paper .
web whqlibdoc.who.int Practitioner – A Practitioner is a health worker such as defined by WHO (in Chapter 1 of the World Health Report 2006 ); a Practitioner might be a physician, nurse, pharmacist, community health worker, district health manager, etc. Practitioners have contact and demographic attributes.
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this profile. Further information about actor and transaction definitions can be found in the IHE Technical Frameworks General Introduction Appendix A: Actors and Appendix B: Transactions .
web profiles.ihe.net This section defines the actors, transactions, and/or content modules in this profile. Further information about actor and transaction definitions can be found in the IHE Technical Frameworks General Introduction Appendix A: Actors and Appendix B: Transactions .
web profiles.ihe.net The Care Services Selective Supplier shall publish an instance CapabilityStatement at the metadata endpoint following ITI Appendix Z.3 using the FHIR capabilities interaction . All supported search parameters and search methods (GET, POST) shall be specified. The search parameters and message semantics defined in [IHE-ITI-90] shall be supported, other parameters may be supported.
web profiles.ihe.net The Care Services Update Supplier shall publish an instance CapabilityStatement at the metadata endpoint following ITI Appendix Z.3 using the FHIR capabilities interaction . All supported interactions shall be specified. The search parameters and message semantics defined in [IHE-ITI-91] shall be supported, other parameters may be supported.
web wiki.ohie.org The OU Update Consumer will use entity matching to determine if there are duplicated sites in the combined data and flag them for review. (See https://wiki.ohie.org/display/documents/OpenHIE+Entity+Matching+Service .)
web www.who.int A developing country has decided to implement a Master Facility List (MFL) based on recommendations from the WHO in the MFL Resource Package . This resource includes a minimum data set to uniquely identify, locate, and contact a specific facility. Since this will be a single source of information for the country, there may be differing hierarchies that need to be supported for the facilities. For example, one hierarchy would be the administrative hierarchy for the country (region, district, county). Another would be the supply chain hierarchy where hubs may be located separately from administrative regions. Yet another could be a reporting hierarchy used to send data to international organizations.
web profiles.ihe.net Actors are expected to follow the recommendations and requirements found in ITI TF-2: Appendix Z.8 “Mobile Security Considerations” .
web profiles.ihe.net There are many reasonable methods of security for interoperability transactions which can be implemented without modifying the characteristics of the transactions in the mCSD Profile. The use of TLS is encouraged, specifically the use of the ATNA Profile (see ITI TF-1: 9 ).
web profiles.ihe.net For guidance on handling challenges regarding the representation of names across multiple languages and in different cultures, refer to the ITI TF-2: 3.24.5.2.3.1 . This section in the ITI Technical Framework describes the use of the language tag as documented in IETF RFC1766 and the HL7 XCN name data type.
web www.ihe.net All referenced terminologies from a Care Services Selective Supplier or Care Services Update Supplier may be pre-coordinated or they may be resolvable from one or more terminology services. Though it is out of scope of the mCSD Profile to define the means of interacting with a terminology service, this could be provided, for example, through the Sharing Valuesets, Codes, and Maps (SVCM) Profile .
web profiles.ihe.net Examples of this kind of federated structure are shown in ITI TF-1: Appendix E.9 , for XCA Responding Gateways.
web profiles.ihe.net The profile is based upon and inspired by the IHE mCSD profile and the use cases and solutions using mCSD are outlined in the mCSD White Paper .
web medcomdk.github.io *The document "Sikkerhedsarkitektur EHMI services v 0.98/Security architechture regarding EHMI central services v 0.98" can be found here (opens a new window)
web www.iso.org ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
Show Usage

Internal Images

eerDiagramWithMSH.png
eerDiagramWithMSH.png
eerDiagramWithoutMSH.png
eerDiagramWithoutMSH.png
eer_eas_1_1_getReceiverDataBySorId.png
eer_eas_1_1_getReceiverDataBySorId.png
eer_eas_1_1_getReceiverDataBySorId_error1.png
eer_eas_1_1_getReceiverDataBySorId_error1.png
eer_getDeviceDataByDeviceId.png
eer_getDeviceDataByDeviceId.png
eer_getDeviceDataByDeviceId_error1.png
eer_getDeviceDataByDeviceId_error1.png
tree-filter.png
tree-filter.png