-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
US Da Vinci CDex (FHIR)
-
STU3
-
Patient Care
-
STU
-
Profiles [deprecated]
-
-
Robert Dieterle / Jay Lyle: 3-0-2
-
Clarification
-
Non-substantive
The Request (Solicited Communication) Examples section seems at odds with the description of some the CommunicationRequest elements (http://hl7.org/implement/standards/fhir/us/davinci-cdex/2019Jun/StructureDefinition-cdex-communicationrequest.html).
.requester - The person or organization creating the CommunicationRequest
.recipient - The recipient(s) of the Communication resulting from this request (not the recipient of the request).
.sender - The sender of the Communication resulting from this request (not the sender of the request).
Note that the last two elements seem to be about the Communication, not the CommunicationRequest resource.
The Example section says "The requester points to the conditionally created organization and its conditionally created endpoint. This is the organization that will receive the requested information when it is returned." but this is more in line with the recipient definition (receiver of the communication). It also says "The recipient points to the contained resource expressing the organization being asked for information" but this would seem to be the sender (source of the communication). Finally, it says "The sender points to the organization that is sending the request" which should be the requester. Please sync up the definitions for the resource elements with the example text. Note that the example files (eg http://hl7.org/implement/standards/fhir/us/davinci-cdex/2019Jun/CommunicationRequest-cdex-example-resource-request.xml.html) may need to be updated too. For example, the resource request example the payer as the sender rather than the requester or recipient.
- is voted on by
-
BALLOT-9328 Negative - Craig Newman : 2019-Sep-FHIR IG CDex R1
- Balloted