Suppress Patient Creation by HL7 Messages - dcm4che/dcm4chee-arc-light GitHub Wiki

Overview

This feature can be used if one wants to suppress the creation of patients in the archive for the configured HL7 messages. If this feature is enabled, the processing of messages will be done only for the already existing patients in the archive. This can be explained as mentioned below :

If creation needs to be suppressed for ADT messages, patient updates/merge will be processed only for existing patients.
If creation of Patients needs to be also suppressed for Order Message Types ORM^01, OMI^O21 or OMG^O19, MWL entries will only be created for existing Patients
If creation of Patients needs to be also suppressed for ORU^R01, reports will only be imported for existing Patients

The suppression of Patient creation is logged in the server.log.

Configuration

Note that one may configure this on Archive Device extension level or on Archive HL7 Application Extension level. The values configured on Archive HL7 Application Extension level will overwrite values configured on Archive Device level.

Using Archive UI

Select the level on which the feature needs to be configured :
- To configure on Archive device level, go to Menu->Configuration, then on Devices page, Edit of dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Again go to its Extensions and Edit extension of Archive device.
- To configure on Archive HL7 application extension level, go to Menu->Configuration, then on Devices page and Edit the dcm4chee-arc device. Go to Extensions and Edit extension of Device Extension. Go to Child Objects and select the HL7 application for which this feature needs to be configured. Go to Extensions and Edit extension of Archive HL7 Application.
Add values of HL7 message types for which one wants to suppress patient creation in field HL7 No Patient Create Message Type and Save.

Using LDAP

One may create a LDIF file and import it to the LDAP Server by using the ldapmodify command line utility.

To configure on Archive device level,

  version: 1
  
  dn: dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
  changetype: modify
  add: hl7NoPatientCreateMessageType
  hl7NoPatientCreateMessageType: OMI^O23

To configure on Archive HL7 application extension level,

  version: 1
  
  dn: hl7ApplicationName=*,dicomDeviceName=dcm4chee-arc,cn=Devices,cn=DICOM Configuration,dc=dcm4che,dc=org
  changetype: modify
  add: hl7NoPatientCreateMessageType
  hl7NoPatientCreateMessageType: OMI^O23

or use the Add Attribute... and Add Value... function of Apache Directory Studio to add attributes on Archive Device level (e.g.: dicomDeviceName=dcm4chee-arc) or Archive HL7 Application level (eg.: hl7ApplicationName=*) in the Archive Configuration.

One may refer to Archive Device or Archive HL7 Application to understand the description of attributes.

Go to the Control tab on Configuration page in archive UI and reload the configuration.

Testing

Send an order feed message containing patient which is not present on archive. One may use query patients service to ensure if patient is present or not in the archive.
```
      hl7snd -c localhost:2575 /path_to_orderMessage.hl7
```
Using the archive UI, query modality worklist entries. One won't find the entries created, if the patient specified in the message is unavailable in the archive.