You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
Additional notes
The text was updated successfully, but these errors were encountered: