Once you begin adding support for overlapping identifiers, you must not use the HL7 module in production until the entire solution is configured to support assigning authorities. Complete all the procedures in this section before using overlapping identifiers in production.
In a typical OnBase installation, each type of identifier (MRN, MPI, and Chart ID) must be unique across all facilities. To allow the same identifier to be used by different objects (for example, because the same MRN exists at different facilities), you must configure OnBase to use assigning authorities. Assigning authorities allow OnBase to differentiate records that have overlapping identifiers.
An assigning authority is the system or organization responsible for assigning an identifier to a particular object. Consider the following example, where both John Smith and Jane Doe have a record with an MRN of 22. John Smith was assigned MRN 22 by the EMR at Facility B. Jane Doe was assigned MRN 22 by the EMR at Facility A.
|
Facility |
Record for John Smith |
Record for Jane Doe |
|---|---|---|
|
Facility A |
MRN 11 |
MRN 22 |
|
Facility B |
MRN 22 |
MRN 33 |
To add support for overlapping identifiers, see the following topics:
-
Configuring AutoFill Keyword Sets for Overlapping Identifiers
-
Configuring Multi-Instance Keyword Groups for Overlapping Identifiers
-
Configuring Medical Document Types for Overlapping Identifiers
-
Configuring HL7 Message Templates for Overlapping Identifiers
-
Configuring HL7 Import Processes for Overlapping Identifiers