Assigning Authority Is Not Configured Correctly - HL7 Module - English - Foundation 22.1 - OnBase - Premier - external - Standard - Essential - Premier - Standard - Essential

HL7 Module
Platform
OnBase
Product
HL7 Module
Release
Foundation 22.1
License
Premier
Standard
Essential

If OnBase is configured to use assigning authorities to distinguish overlapping identifiers (MRNs, MPIs, or Chart IDs), then the Medical Records Chart message action requires messages to contain a non-blank assigning authority value.

  1. Identify the HL7 import process that encountered the failure.
  2. In OnBase Configuration, open the import process's configuration.
  3. Identify the field mapped to the Assigning Authority chart data field.
    1. Click View Mappings in the HL7 Process Settings dialog box.
    2. Take note of the HL7 field that specifies Assigning Authority in the Data Field column. This is the HL7 field where the Assigning Authority chart data field is mapped to.
    3. Make sure the Assigning Authority chart data field is assigned to a component in the same HL7 field as the identifier component.
    4. Click OK to close the Assigned Mappings dialog box.
  4. In hl7failedmessages.txt, check the field where the assigning authority is expected.

    • If the field is empty, then the sending application must be configured to send either a valid assigning authority or the HL7 null value (two single or double quotation marks). If this cannot be accomplished using the sending application or HL7 interface engine, the OnBase HL7 module can be configured to add values to incoming messages by using VBScript.

    • If the field contains a value, make sure the value does not exceed the allowed maximum of 50 characters.

    • The combination of the identifier value and assigning authority value must uniquely identify a medical record across all facilities in the system. If the message specifies an existing medical record in OnBase, make sure the identifiers in the message match the identifiers on the existing record.