Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
US Core (FHIR)
-
7.0.0-ballot
-
Cross-Group Projects
-
US Core Procedure Profile
US Core ServiceRequest Profile -
-
Eric Haas/Jason Vogt: 25-0-0
-
Clarification
-
Non-substantive
Description
The current text explaining how the reason can be documented is exactly applied per the Jira agreed to, but it seems we missed some relevant attributes names in the ServiceRequest.reason.... attributes. It states:
- *The Reason or justification for a referral or consultation is communicated through:
- ServiceRequest.reason or ServiceRequest.reason, and Procedure.basedOn that links the Procedure to the US Core ServiceRequest Profile.
This is missing "Code" and "Reference" on the attribute names and should actually state on Procedure: * *The Reason or justification for a referral or consultation is communicated through:
- Procedure.basedOn that links the Procedure to the US Core ServiceRequest Profile that includes either ServiceRequest.reasonCode or ServiceRequest.reasonReference.
And on ServiceRequest: * *The Reason or justification for a referral or consultation is communicated through:
- ServiceRequest.reasonCode or ServiceRequest.reasonReference on the ServiceRequqest according to the US Core ServiceRequest Profile that Procedure.basedOn references.
Note the small adjustment in phrasing to read it better in context of the resource where the text appears.
Attachments
Issue Links
- is voted on by
-
BALLOT-57994 Negative - Hans Buitendijk : 2024-Jan-FHIR US CORE E7 STU
- Balloted
-
BALLOT-60160 Negative - Frank Oemig - Cerner : 2024-Jan-FHIR US CORE E7 STU
- Balloted