-
Notifications
You must be signed in to change notification settings - Fork 4
UAT: Update author source for labs (3.1 spec) #1453
Copy link
Copy link
Open
Labels
FHIR conversion requiredThis ticket will require FHIR conversion workThis ticket will require FHIR conversion workjurisdiction needTickets that directly impact users' ability to use our appTickets that directly impact users' ability to use our appstreamline eCRIssues for the Streamline eCR teamIssues for the Streamline eCR teamuser requestA feature or bugfix directly requested by users.A feature or bugfix directly requested by users.
Metadata
Metadata
Assignees
Labels
FHIR conversion requiredThis ticket will require FHIR conversion workThis ticket will require FHIR conversion workjurisdiction needTickets that directly impact users' ability to use our appTickets that directly impact users' ability to use our appstreamline eCRIssues for the Streamline eCR teamIssues for the Streamline eCR teamuser requestA feature or bugfix directly requested by users.A feature or bugfix directly requested by users.
Type
Fields
Give feedbackNo fields configured for issues without a type.
What needs to be done
Under the 3.1 spec, authors for labs should now come from
/ClinicalDocument/component/structuredBody/component/section/entry/organizer/author/assignedAuthor/representedOrganizationBut we currently only pull author from the following xpath, which is no longer required by 3.1 spec.
/ClinicalDocument/component/structuredBody/component/section/entry/organizer/performer/representedOrganization.Update the DiagnosticReport author extraction logic to prioritize the
author/assignedAuthor/representedOrganizationpath. If that path is not present, fall back toperformer/representedOrganizationto maintain backward compatibility with older documents.Open question: Note that it is possible that an entry/organizer would have both a performer and an author. Can both exist in a FHIR bundle, and if so, which field should we pull the author from on the Viewer-side?
Why it needs to be done
Brought up by TN -- Hardik will provide de-identified examples when possible.
Acceptance Criteria
Technical Notes
FHIR conversion IS required for this ticket.
Additional context
Relevant files:
data/Templates/eCR/Entry/Result/entry.liquidExample eCRs: [TBD - will be provided by TN]