Country-Specific

Integrations for use cases specific to outside the United States.

Denmark

Epic supports exchanging messages between organizations in Denmark using interfaces that are certified to MedCom standards, exchanged over a Value Added Network Services (VANS) network provider.

Epic also exchanges medication orders, prescriptions, and administrations with the national Fælles Medicinkort (FMK) database. This allows a patient’s medication list to be viewable across the continuum of care in Denmark, e-prescriptions to be filled at the patient’s pharmacy of choice, and administrations given by home care nurses and clinics to be recorded centrally.

The sections below describe interfaces used by organizations in Denmark.

Outgoing Hospital Notification

Sends hospital notification messages to Danish municipalities. This interface can send ED arrival, admission, discharge, leave of absence, and death notifications. The messages follow the MedComHospitalNotificationMessage profile specifications.

Incoming FHIR Message Acknowledgement - Denmark

Receives asynchronous acknowledgement messages in response to any MedCom FHIR messages sent from Epic.

Outgoing Municipality Integrations

Manages communication with external municipal systems according to established MedCom protocols to coordinate the delivery of home care after discharge. The outgoing interface supports: automatic admission and discharge notifications to alert municipalities when their citizens have been admitted to and discharged from the hospital, clinical reports by nursing staff to convey updated clinical information and home care needs to the home care system so they can prepare to assume responsibility for the patient, and administrative notifications to coordinate and document the extension of admissions if the municipality is not yet prepared to accept responsibility for patient care. This integration also includes an incoming interface for filing admission reports sent by municipality home care systems when they receive an admission notification from the hospital. Clinical staff can use these admission reports to review the current status of home care patients. This interface uses the Medcom XML/EDIFACT standard.
Current integrations include
  • MEDCOM Information Systems

Bidirectional Correspondence read the specBidirectional Correspondence technical specification

Sends and receives patient-centric clinical correspondence messages to external parties, including other hospitals, general practitioners, and municipal systems. These messages are used for ad hoc communication to convey additional information beyond what is included in other specifications.
Current integrations include
  • MEDCOM Information Systems

Outgoing Newborn CPR Assignment Request and Response

Registers newborns in the Danish civil registration system (CPR) and reserves a corresponding CPR identifier (national ID). This interface uses the Medcom Web Service standard.

Outgoing Order Requisitions

Sends orders placed by a clinical user to either an external LIS or Danish laboratory outside the organization. This interface supports general chemistry, blood bank, microbiology, and pathology laboratory procedures placed by users in EpicCare Inpatient and EpicCare Ambulatory, and pathology procedures placed by clinical users in OpTime. This interface uses the Medcom XML standard.

Incoming Pathology Results

Receives pathology test results from a LIS for use in Epic. Results can be received for orders placed in Epic or placed elsewhere. Additionally, this interface can update the status of the results to In Process, Preliminary, Final, or Final-Edited. This interface uses the Medcom XML standard.

Incoming Lab Results Interface

Receives general chemistry, blood bank, and microbiology test results from LIS for use in Epic. Results can be received for orders placed in Epic or placed elsewhere. Additionally, this interface can update the status of the result to In Process, Preliminary, Final, or Final- Edited. This interface uses the Medcom XML standard.

Outgoing Referrals and Booking Confirmation

Manages outgoing referrals communication with external systems according to established MedCom protocols. The interface facilitates sending new referrals composed in Epic and forwarding copies of previously received referral messages. The interface can also send booking confirmations to inform a patient's referring and primary care physicians when a referral is being acted on in Epic. These notifications can be sent automatically when an appointment has been scheduled, or when a patient is preadmitted or arrived in the ED for an issue relating to the referral. This interface uses the Medcom XML/EDIFACT standard.
Current integrations include
  • MEDCOM Information Systems

Incoming Referrals and Booking Confirmation

Manages incoming referrals communications with external systems according to established MedCom protocols. This interface can both create incoming hospital referrals and file booking confirmation messages for referrals originating in Epic.
Current integrations include
  • MEDCOM Information Systems

Outgoing Binary Documents

Sends binary attachment documents associated with a MedCom message. This interface must work in conjunction with one of the following MedCom interfaces: Outgoing Summary of Care, Outgoing Referrals and Booking Confirmation, Bidirectional Correspondence, and Outgoing Order Requisitions.
Current integrations include
  • MEDCOM Information Systems

Incoming Binary Documents

Files the binary attachment documents associated with an incoming MedCom message to the Epic WebBLOB server. This interface must work in conjunction with one of the following MedCom interfaces: Incoming Summary of Care, Incoming Referrals and Booking Confirmation, Bidirectional Correspondence, Outgoing Municipality Integrations - Incoming Response, Incoming Rehabilitation Plan Summary, Incoming Lab Results, and Incoming Pathology Results.
Current integrations include
  • MEDCOM Information Systems

Incoming Summary of Care Interface

Files a summary of care document (Epikrise) from an external hospital or specialist as a note to the patient's chart. These notes describe the care that the patient received from the external hospital or specialist and can be used as reference when providing care in Epic.
Current integrations include
  • MEDCOM Information Systems

Outgoing Summary of Care Interface

Sends a summary of care document (Epikrise) to the patient's referring provider and primary care physician to report the outcome of an ED visit, admission, or ambulatory encounter using a combination of discrete and free-text information. Summary of care messages are automatically sent for the patient whenever a designated Epikrise note has been signed and the patient's encounter is closed. This interface uses the Medcom XML/EDIFACT standard.
Current integrations include
  • MEDCOM Information Systems

Outgoing FMK Medication Card Services Request and Response read the specOutgoing FMK Medication Card Services Request and Response technical specification

Manages the following interactions between Epic and the Danish medication database Falles Medicinkort (FMK): Filing medication lists for patients into Epic; pushing medication changes from Epic to the national database; and setting the reviewed status of the medication list by a clinician.

Outgoing Birth Notification Interface read the specOutgoing Birth Notification Interface technical specification

Sends a report to register newborns in the municipal child care system and begin coordination of home visits by municipal pediatric nursing after discharge.
Current integrations include
  • MEDCOM Information Systems

Outgoing ECPR Assignment Request and Response

Requests ECPR identifiers for request a new official ECPR from the Denmark national ECPR registry for non-Danish residents, anonymous, trauma, and unknown patients.

Outgoing Rehabilitation Plan Summary

Sends a summary of the physical therapy/rehabilitation (GGOP) provided for a patient and needs for ongoing therapy/rehab. Frequently used as a way for physical therapists to document ongoing care for a patient, provide progress updates to external parties such as their primary care physician, and transition responsibility for therapy to other entities such as other hospitals or municipality rehabilitation systems. This interface uses the XML (DGOP), GGOP (MedCom XML) standard.
Current integrations include
  • MEDCOM Information Systems

Incoming Rehabilitation Plan Summary

Receives incoming summaries of physical therapy/rehabilitation (GGOP) from physical therapists. This interface can be configured to create scheduling orders, which users can use to plan future appointments for the patient's care. This interface uses the XML (DGOP) GGOP (MedCom XML) standard.
Current integrations include
  • MEDCOM Information Systems

Outgoing FMK Ordered Refill Request and Response read the specOutgoing FMK Ordered Refill Request and Response technical specification

Sends refill requests to the Danish medication database Fælles Medicinkort (FMK) for a patient or an entire facility.

Incoming Rehabilitation Plan Summary

Receives incoming summaries of physical therapy/rehabilitation (GGOP) from physical therapists. This interface can be configured to create scheduling orders, which users can use to plan future appointments for the patient's care. This interface uses the XML (DGOP) GGOP (MedCom XML) standard.

Incoming Receipts read the specIncoming Receipts technical specification

Receives receipts for messages sent to the VANS network in relation to the Medcom message sent.

Outgoing Receipts read the specOutgoing Receipts technical specification

Sends positive or negative receipt messages for Medcom messages received from the VANS network using the Medcom XML/EDIFACT standard.