Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update MSH-4 Field to Use CLIA Instead of OID #17287

Closed
1 of 4 tasks
MikaelahD13 opened this issue Feb 6, 2025 · 1 comment · May be fixed by #17333
Closed
1 of 4 tasks

Update MSH-4 Field to Use CLIA Instead of OID #17287

MikaelahD13 opened this issue Feb 6, 2025 · 1 comment · May be fixed by #17333
Assignees
Labels
Arkansas engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.

Comments

@MikaelahD13
Copy link
Collaborator

MikaelahD13 commented Feb 6, 2025

Problem statement

CDC Prime result messages currently contain an OID in the MSH-4 field. However, ADH requires this field to contain a CLIA instead. The issue needs to be resolved to ensure compliance with ADH requirements.

What you need to know

We will need to set-up a transform that specifies a CLIA for each sender that can send to Arkansas through the Covid Pipeline and the UP.

To the Covid pipeline receivers update their MSH-4 settings to this:

  "MSH-4": [
      {
        "*": "CDC PRIME^11D2030855^CLIA"
      }

In the UP add this transform to Arkansas receiver transforms:

  - name: co-reporting-facility-name
    value: [ '"CDC PRIME"' ]
    hl7Spec: [ MSH-4-1 ]

  # MSH 4-2
  - name: co-reporting-facility-id
    value: [ '"11D2030855"' ]
    hl7Spec: [ MSH-4-2 ]

  # MSH 4-3
  - name: co-reporting-facility-id-type
    value: [ '"CLIA"' ]
    hl7Spec: [ MSH-4-3 ]
  • ADH has reported that MSH-4 should contain a CLIA identifier rather than an OID.

  • This change will impact how results are processed by ADH and may require updates to the message transformation logic.

  • Ensuring that the correct CLIA is used in MSH-4 is critical for accurate data processing and compliance.

Acceptance criteria

  • For Arkansas, MSH-4 contains CLIA for both CP and UP
@MikaelahD13 MikaelahD13 added the onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. label Feb 6, 2025
@chris-kuryak chris-kuryak added engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team Kansas Arkansas and removed Kansas labels Feb 6, 2025
@lucero-v lucero-v self-assigned this Feb 10, 2025
@lucero-v lucero-v linked a pull request Feb 11, 2025 that will close this issue
4 tasks
@lucero-v
Copy link
Collaborator

Updated UP azure schema in Prod and Staging. Also changed the settings directly for the CP.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Arkansas engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants