HL7 Receivers feeding MWL SCPs - amsalama/dcm4chee-arc-light GitHub Wiki

DCM4CHEE Archive may be configured to receive HL7 messages on one or more receivers i.e. HL7 Applications listening on one common or different HL7 Network Connection. These could be used to feed a common or multiple HL7 receiver specific MWL SCPs. Alternatively, the individual created HL7 applications may also be used to configure receiving application facility specific attribute coercions for incoming MWL C-Find requests to the archive.

Default archive configuration is pre-configured with 2 HL7 specific network connections listening on ports 2575 and 12575 (TLS). Depending on one's requirements, one may choose to clone these network connections listening on different ports and use these network connections in the HL7 application as required.

• Go to Configuration -> Devices -> dcm4chee-arc -> Child Objects -> Network Connections.
• Use Clone this Network Connections part against 2575 hl7 or 12575 hl7-tls network connection.
• Choose a different Port and rename the Name and Save.

By default, the archive is pre-configured with a * HL7 Application which implies that it can receive any of the configured accepted message types irrespective of the Receiving application and facility name (MSH-5 and MSH-6) values in the incoming HL7 messages.

Depending on the use cases as required in one's archive, one may choose to clone the default HL7 Application of the archive and rename these cloned HL7 applications to match the values in incoming HL7 message's Receiving application and facility name (MSH-5 and MSH-6) fields. This can be particularly useful if one wants to have customized stylesheets for HL7 to MWL mapping specific only to certain receiving application and facilities. Another use case to have individual HL7 applications would be if one wants to configure attribute coercions for MWL C-FIND requests specific only for certain receiving application and facilities.

• Go to Configuration -> Devices -> dcm4chee-arc -> Extensions -> Device Extension -> Child Objects -> HL7 Application.
• Use Clone this HL7 Applications part against * from list of HL7 Applications.
• Rename the HL7 Application Name to match with values corresponding to MSH-5 and MSH-6 fields of the HL7 messages for eg. DEPARTMENT-A|HOSPITAL-A.
• Optionally, the Network Connection Reference may be changed to reference it to a different HL7 Network Connection.
• Save the configuration.

Each HL7 Application is associated with a local Application Entity. This is done in order that, when studies corresponding to the MWL orders are received by the archive, they can be correctly associated with one another. By default, the local AE associated with HL7 applications is DCM4CHEE. As per one's requirements, if required, one may choose to have different AEs associated with different HL7 Applications. For this,

• Go to Configuration -> Devices -> dcm4chee-arc -> Child Objects -> Network AEs.
• Use Clone this Network AEs part against DCM4CHEE from the list of application entities.
• Rename AE Title and Save.
• Go to Configuration -> Devices -> dcm4chee-arc -> Extensions -> Device Extension -> Child Objects -> HL7 Application.
• Select the created / clone HL7 Application from the list.
• Go to its Extensions -> Archive HL7 Application -> Edit extension -> Attributes.
• Select the created / clone AE for AE Title field and Save.

The stylesheets used to transcode the incoming HL7 messages (ADT, orders, ORU) are pre-configured on archive device level by default. These stylesheets, if required, may be customized and configured either on archive device level - whereby they will be applied to all incoming respective HL7 messages. Or one may choose to configure these customized stylesheets on the individually configured HL7 Applications as required.

• Go to Configuration -> Devices -> dcm4chee-arc -> Extensions -> Device Extension -> Child Objects -> HL7 Application.
• Select the HL7 Application that was created / cloned.
• Go to its Extensions -> Archive HL7 Application -> Edit extension -> Attributes.
• Depending upon which stylesheet one customized, configure this for ADT, orders and / or ORU and Save.

By default, there is no pre-configured Attribute Coercion to coerce incoming MWL C-Find requests to the archive. As per one's requirements one may choose to have one common attribute coercion configured on archive device level or choose to configure it on archive AE level.

For configuring on archive device level :

• Go to Configuration -> Devices -> dcm4chee-arc -> Extensions -> Device Extension -> Extensions -> Archive Device -> Edit extension -> Child Objects -> Attribute Coercion -> Add.

For configuring an attribute coercion specific to a HL7 receiver :

• Go to Configuration -> Devices -> dcm4chee-arc -> Child Objects.
• Select the created / cloned or default DCM4CHEE AE associated with HL7 application.
• Go to its Extensions -> Network AE Extension -> Edit extension -> Extensions -> Archive Network AE -> Edit extension -> Child Objects -> Attribute Coercion -> Add.