This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
This is the narrative for the resource. See also the XML or JSON format. This example conforms to the profile Conformance.
(Requirements Definition)
Published: 2015-04-02 (draft)
Published by: U.S. Office of the National Coordinator (ONC)
This profile defines the expected capabilities of the DAF Requestor actor when conforming to the DAF FHIR IG.
FHIR Version: | 1.4.0 (DSTU2) |
---|---|
Supported formats: | JSON or XML |
The DAF Requestor SHALL support accessing at least one FHIR resource using the appropriate DAF profile(s) for the resource being accessed. The DAF Requestor SHALL implement REST behavior according to the FHIR specification. The DAF Requestor SHALL support either json or xml resource formats for all DAF interactions.
DAF Requestors MAY use the following common parameters as part of queries related to DAF profiles:
DAF Requestors SHOULD use the following common parameters as part of queries related to DAF profiles to avoid repeated queries.
DAF Requestors MAY use the following search contexts defined within the FHIR specification.
DAF Requestors MAY use Modifiers as applicable to the data types of the search parameters to access data. DAF Requestors MAY use any search parameters that are appropriate for querying a particular FHIR resource, however they can only count on the search parameters that are identified as SHALL within the DAF Responder's conformance statement to be used in the execution of the search. For a complete list of search parameters that are available, please refer to DAF Responder's conformance statement and the search parameters supported by the base FHIR resources profiled by DAF.
Security:
Implementations must meet the security requirements documented in the DAF implementation guide.
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.