Use APHL assigned OIDs for MSH-3 and MSH-4

[mpbrown]

What needs to be done

Use IDs assigned from APHL for MSH-3 Sending Application and MSH-4 Sending Facility

Why it needs to be done

So STLTs can expect predetermined ids from SR in the HL7 message header.

A fake aggregate CLIA was assigned to SimpleReport by APHL so that STLTs can more easily process HL7 messages based on MSH-4 Sending Facility. If we populated MSH-4 with the real facility CLIA instead of SimpleReport's fake CLIA, then many STLTs would need to frequently reconfigure their systems with a long list of possible facility CLIAs to accept. To make this easier for STLTs, APHL assigns a fake CLIA to "aggregate senders" like SimpleReport.

Acceptance Criteria

MSH-3 Sending Application

• In Prod, use:
  • namespace: SIMPLEREPORT.PROD
  • oid: 2.16.840.1.113883.3.8589.4.2.134.1
  • id type: ISO
• In all non-prod environments including local, use:
  • namespace: SIMPLEREPORT.STAG
  • oid: 2.16.840.1.113883.3.8589.4.2.134.2
  • id type: ISO

MSH-4 Sending Facility

• In ALL environments including prod, use:
  • namespace: CDC.SimpleReport
  • universal id CLIA: 00Z0000064
  • id type: CLIA

In all other HL7 fields:

• As of 11/4/2025, APHL stated we should continue to use the existing CDC OID 2.16.840.1.114222.4 for other HL7 fields like ORC-3.3 where SimpleReport is identified as the assigning authority.