Details
-
Change Request
-
Resolution: Persuasive with Modification
-
Medium
-
US Core (FHIR)
-
5.0.1
-
Cross-Group Projects
-
US Core Fetch DocumentReference
-
-
Eric Haas/Brett Marquard: 13-0-1
-
Enhancement
-
Non-compatible
Description
See https://chat.fhir.org/#narrow/stream/179166-implementers/topic/.24docref.20operation.20Q
It is currently unclear how DocumentReferences should be matched based on the type parameter. Does a matching instance need to contain all codings of the "type" parameter or just one? Should the .text element of the "type" parameter be considered for matching?
The recommendation of the Zulip thread above would be to change the "type" parameter to 0..* Codings.