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

CVS Sender Transforms for removing OBX segments and mapping to valid SNOMED codes #17399

Open
2 tasks
chris-kuryak opened this issue Feb 21, 2025 · 0 comments · May be fixed by #17437
Open
2 tasks

CVS Sender Transforms for removing OBX segments and mapping to valid SNOMED codes #17399

chris-kuryak opened this issue Feb 21, 2025 · 0 comments · May be fixed by #17437
Assignees
Labels
engineering Work to be completed by an engineer onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. sender Analytics label to flag work related to Sender features support Analytics label to flag work related to Org issues once they've gone live

Comments

@chris-kuryak
Copy link
Collaborator

chris-kuryak commented Feb 21, 2025

Problem statement

CVS has requested some Sender transforms be created for their HL7 connection before they can meet ReportStream's NIST validation requirements.

What you need to know

  • From CVS:
    • OBX (4-6) from below are metadata fields that we are actively trying to suppress in Epic as they don’t need to be shared externally. That changes may take several months, but you will notice they will be missing LOINC codes. Can you set a rule on your end to ignore OBX segments with missing LOINC codes? Or to your point, you can look for lot#, expiration, internal controls, and test brand.
    • We practically cannot send snomed codes with our current build. Can reportstream assist with converting our results and spec type to snomed? I can share our mappings today for the DOH file extracts as we hardcode these in:
      Positive = 260373001
      Negative = 260415000
      Invalid = 455371000124106
      Specimen type OTHER = 445297001
  • Because they're only sending a String for OBX-5, the value under OBX-2 is ST. Once we transform the message to have a SNOMED code in OBX-5 the data type of the OBX segment will need to be CWE. An additional transform is needed for that.

Acceptance criteria

  • CVS changes made per above requirements
  • Changes tested with CVS team members to ensure transforms meet expectations
@chris-kuryak chris-kuryak added 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. sender Analytics label to flag work related to Sender features support Analytics label to flag work related to Org issues once they've gone live labels Feb 21, 2025
@chris-kuryak chris-kuryak changed the title CVS change request CVS Sender Transforms for removing OBX segments and mapping to valid SNOMED codes Feb 21, 2025
@lucero-v lucero-v self-assigned this Feb 24, 2025
@chris-kuryak chris-kuryak removed the needs-refinement Tickets that need refinement from the team label Feb 25, 2025
@lucero-v lucero-v linked a pull request Feb 25, 2025 that will close this issue
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Work to be completed by an engineer onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. sender Analytics label to flag work related to Sender features support Analytics label to flag work related to Org issues once they've gone live
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants