Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
US Core (FHIR)
-
5.0.1
-
Cross-Group Projects
-
US Core Server CapabilityStatement
-
12.2.1.4.2
-
-
Eric Haas/Brett Marquard: 13-0-1
-
Enhancement
-
Non-substantive
Description
Currently, there is no conformance expectation around 'resolves' which means the certification will treat as a MAY (typically we don't list the MAYs). The original intent was it was to be interpreted as a SHOULD, but at the time adding primitive extensions to the script was not possible. Since primitive extensions are now supported, I will add to server conformance expectations:
Element: CapabilityStatement.rest.resource.referencePolicy
| resolves | Resolves References | The server will attempt to resolve logical references to literal references - i.e. converting Reference.identifier to Reference.reference (if resolution fails, the server may still accept resources; see logical). |