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

Content

• Overview
• Configuration
  • HL7 Network Connection
  • HL7 Application
    • HL7 Application associated AE
    • HL7 Application Destination MWL SCP - until v5.29.2
    • HL7 Application MWL Worklist Label - v5.30.0 onwards
  • HL7 to MWL Mapping
  • MWL C-FIND Requests Attribute Coercions

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 HL7 applications are used to feed a common or multiple HL7 receiver specific MWL SCPs.

Optionally, attribute coercions for coercing incoming MWL C-Find requests to the archive may be configured specific to HL7 applications of 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 specific 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 to facilitate storage of structured text or encapsulated PDF reports in HL7 ORU messages received by the archive. By default, the local AE associated with HL7 applications is DCM4CHEE. Optionally choose to associate different AEs with different HL7 Applications of archive.

• 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.

Note : This field is available only upto archive version 5.29.2

Each HL7 Application may be associated with a destination Application Entity to facilitate separation of DICOM Modality Worklists during creation on receive of HL7 order messages.

By default, there is no destination AE configured on default HL7 application *, implying the created MWL items will be provided by all configured MWL SCPs of the archive.

Optionally choose to configure specific AE on default (*) / specific HL7 application(s) of the archive.

• 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 Destination MWL SCP field and Save.

Note : The AE configured as Destination MWL SCP may be used to configure attribute coercions specific to MWL C-FIND requests received by this AE

Note : This field is available only in archive versions 5.30.0 onwards

Each HL7 Application may be associated with a Worklist Label (0074,1202) to facilitate separation of DICOM Modality Worklists during creation on receive of HL7 order messages.

By default, there is no MWL Worklist Label configured on default HL7 application *, implying created MWL items are not bound to a particular MWL Worklist and are provided by all Archive AEs with MWL SCP Transfer Capability.

Optionally choose to configure specific Worklist Label on default (*) / specific HL7 application(s) of the archive, by configuring one or more UI MWL Worklist Label(s).

These configured UI MWL Worklist Labels can then be selected in MWL Worklist Label of the HL7 application.

The stylesheet used to transcode incoming HL7 order messages are pre-configured on archive device level (applied to incoming HL7 order messages) by default.

• Go to Configuration -> Devices -> dcm4chee-arc -> Extensions -> Device Extension -> Archive Device Extension -> Attributes.
  • Schedule Procedure Template URI

Refer HL7 Order to DICOM MWL Mapping to understand mappings between HL7 order message fields and DICOM Modality Worklist attributes.

Optionally, this stylesheet may be customized and configured on archive's HL7 Applications extension level (applied only to incoming HL7 order messages received by these individual HL7 Applications of archive).

• 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. Edit following field pointing to your custom stylesheet
  • Schedule Procedure Template URI
• Save the configuration.
• Optionally, choose to add your custom stylesheet in archive's Vendor Data

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.