Details
-
Question
-
Resolution: Considered - Question answered
-
Highest
-
US Core (FHIR)
-
3.1.1
-
Cross-Group Projects
-
Clinical Notes Guidance [deprecated]
-
4.2
-
To protect clients from potentially missing important information in another resource type the guide requires servers to "expose these reports through both DiagnosticReport and DocumentReference"
and this excerpt:
To protect clients from potentially missing important information in another resource type the guide requires servers to "expose these reports through both DiagnosticReport and DocumentReference" see http://build.fhir.org/ig/HL7/US-Core/clinical-notes-guidance.html#fhir-resources-to-exchange-clinical-notes and this excerpt:
Description
Since this isn’t required, what does in fact protect clients from potentially missing important information in another resource type? Can clarifying language be added to this section?
Existing Wording:
The developers of this guide considered requiring Clients query both DocumentReference and DiagnosticReport to get all the information for a patient. However, the requirement to query two places is potentially dangerous if a client doesn’t understand or follow this requirement and queries only one resource type thereby potentially missing important information from the other type.
(Comment 23 - imported by: Jean Duteau)
Attachments
Issue Links
- is voted on by
-
BALLOT-14926 Affirmative - Celine Lefebvre : 2021-Jan-FHIR US CORE R1 STU2 STU
- Closed
