FHIR RESTful Capabilities

Specialty Rx Data Recipient SHALL:

1. Support the Unsolicited workflow defined in this Guide and respond to the $process-message operation carrying a Specialty Rx Query Response - Unsolicited.
2. Support the json source format.
3. Declare a CapabilityStatement identifying the profiles supported.

Specialty Rx Data Recipient SHOULD:

1. Support the xml source format.
2. Identify the Specialty Rx profiles supported as part of the FHIR meta.profile attribute for each applicable instance.

The Specialty Rx Data Recipient MAY

1. Support the Solicited workflow defined in this Guide, including the Specialty Rx Query, Specialty Rx Query Response, and Specialty Rx Error messages.
2. Support the Patient/$match operation.

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 co

Resources

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

• Task interactions are RESTful.

• OperationOutcome interactions are within both messaging and RESTful actions.

Messaging