Loading...

XML

Word

Printable

JSON

Specification:

FHIR Core (FHIR)
Raised in Version:

R4
Work Group:

Clinical Decision Support
Related URL:
http://hl7.org/fhir/guidanceresponse-definitions.html#GuidanceResponse.reasonReference
Related Artifact(s):

GuidanceResponse
Grouping:
- Block-Vote-1
Resolution Description:

Hide

Agreed, change to a CodeableReference to any resource, but add guidance in the comments that:

1) Although this reference can be used to point to any resource, it is typically expected to refer to subject-specific data appropriate to the subject of the guidance. For example, patient-based decision support would be expected to reference patient-level data.

2) Refer specifically to the targetPath and targetElement extensions as the preferred mechanism for referring to paths within the resource.

Show
Agreed, change to a CodeableReference to any resource, but add guidance in the comments that: 1) Although this reference can be used to point to any resource, it is typically expected to refer to subject-specific data appropriate to the subject of the guidance. For example, patient-based decision support would be expected to reference patient-level data. 2) Refer specifically to the targetPath and targetElement extensions as the preferred mechanism for referring to paths within the resource.
Resolution Vote:
Abdullah Rafiqi/Ben Hamlin: 19-0-0
Change Category:
Enhancement
Change Impact:
Non-compatible
Applied for Version:

R5

In R4, GuidanceResponse.reasonReference is limited to Reference(Condition | Observation | DiagnosticReport | DocumentReference).

Propose allowing reasonReference to reference any resource in R5.

Also, we need a way to specify a path within that referenced resource.