FHIR RESTful Capabilities

Specialty Rx Data Source SHALL:

1. Support the Solicited workflow defined in this guide by responding to the $process-message operation containing a Specialty Rx Query message by returning a Specialty Rx Query Response message or Specialty Rx Error message.
2. Support all required RESTful searches and search parameters.
3. Support the JSON source format.
4. Declare a CapabilityStatement identifying the profiles supported.

Specialty Rx Data Source SHOULD:

1. Respond to the Patient/$match operation.
2. Support the XML source format.
3. Identify the Specialty Rx profiles supported as part of the FHIR meta.profile attribute for each applicable instance.

The Specialty Rx Data Source MAY

1. Support the Unsolicited workflow defined in this guide, using the Specialty Rx Query Response - Unsolicited message.
2. Support the Task / SMART application launch capability specified in the guide.

Security

1. For general security considerations refer to FHIR Security and Privacy Considerations.
2. For additional security guidance, refer to the core FHIR Security guidance page.
3. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.

Resources

• AllergyIntolerance, Condition, Coverage, DocumentReference, MedicationRequest and Observation actions referenced below are executed in the context of message processing.

• Task interactions referenced below are RESTful.

• OperationOutcome interactions referenced below are within both messaging and RESTful actions.

Search

Data Source systems SHALL follow US Core search requirements and guidance when performing searches associated with this guide. See the Search Conventions section.

Messaging