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

Add equipment UID type to FHIR bundles #6642

Closed
mehansen opened this issue Sep 26, 2023 · 0 comments · Fixed by #6840
Closed

Add equipment UID type to FHIR bundles #6642

mehansen opened this issue Sep 26, 2023 · 0 comments · Fixed by #6840
Assignees
Labels
ReportStream Issues stemming from ReportStream feedback

Comments

@mehansen
Copy link
Collaborator

mehansen commented Sep 26, 2023

Background

ReportStream has asked us to send equipment UID type for devices in our FHIR messages as part of their effort to onboard NY to the Universal Pipeline. Once we have equipment UID type stored for our device type diseases, we can include it in the FHIR bundle under Observation.device.identifier.type.coding.code. This work is blocked by the ticket to add equipment UID type to the LIVD sync.

Action requested

Wherever we can deduce it for a test event, add equipment UID type to its FHIR bundle under Observation.device.identifier.type.coding.code for the result Observations.

Acceptance criteria

  • result Observations contain equipment UID type when we are sending test result info with a device that has a valid value for this field. we have a valid value if:
    • for single-entry, the device used has an equipment UID type in the Device Type Disease table
    • for bulk upload, if the user-provided device info maps to a device that has equipment UID type in the Device Type Disease table
  • AoE Observations are not changed

Additional notes

@mehansen mehansen removed the Blocked label Oct 23, 2023
@mehansen mehansen added this to the Support NY on the UP milestone Oct 23, 2023
@fzhao99 fzhao99 self-assigned this Oct 24, 2023
@mehansen mehansen added the ReportStream Issues stemming from ReportStream feedback label Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ReportStream Issues stemming from ReportStream feedback
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants