Loading...

XML

Word

Printable

JSON

Specification:

US Da Vinci CRD (FHIR)
Raised in Version:

1.0.0 [deprecated]
Work Group:

Clinical Decision Support
Related URL:
http://build.fhir.org/ig/HL7/davinci-crd/hooks.html#linkage-between-created-resources
Related Page(s):

Supported Hooks
Related Section(s):
4.3.2.4.2
Grouping:
- Block-Vote-8
Resolution Description:

Hide

There's no conflict. When executing the POST, you absolutely ignore the id. I.e. you don't create the record at the location of the specified id. However, you DO use the id for managing relationships between resources. If an action says "create record A, then create record B that points to record A", you must have a way of doing that. We don't have fullUrl available in CDS Hooks, but we can accomplish the same thing just using the resource ids.

If there is specific clarifying language you think should be added, you could propose.

Show
There's no conflict. When executing the POST, you absolutely ignore the id. I.e. you don't create the record at the location of the specified id. However, you DO use the id for managing relationships between resources. If an action says "create record A, then create record B that points to record A", you must have a way of doing that. We don't have fullUrl available in CDS Hooks, but we can accomplish the same thing just using the resource ids. If there is specific clarifying language you think should be added, you could propose.
Resolution Vote:
Lloyd McKenzie / Bob Dieterle: 19-0-3

The proposal in http://build.fhir.org/ig/HL7/davinci-crd/hooks.html#linkage-between-created-resources to use FHIR Transaction processing rules conflicts with the details around "id" in the FHIR create interaction where it says "id" is optional, and if provided, it SHALL be ignored.