Generated Narrative: CapabilityStatement rtpbc-responder

RTPBC Responder Capability Statement

  • Implementation Guide Version: 2.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats: application/json-patch+json
  • Published on: 2019-12-08 00:00:00-0500
  • Published by: HL7 International / Pharmacy

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Mode: server

RTPBC Responder SHALL: 1. Support the $process-message operation. 2. Support at least one use case defined in this IG and listed in the Use Cases section. 3. Implement the RESTful behavior according to the FHIR specification. 4. Support the JSON source format. 5. Provide on the server a CapabilityStatement identifying the profiles supported. RTPBC Responder SHOULD: 1. Support the XML source format. 2. Identify the RTPBC profiles supported as part of the FHIR meta.profile attribute for each instance.

Security

Implementers are expected to follow core FHIR security principles (https://www.hl7.org/fhir/security.html).In addition, the FHIR Security and Privacy Module (http://hl7.org/fhir/R4/secpriv-module.html) describes how to protect patient privacy. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.

Summary of System-wide Operations
ConformanceOperationDocumentation
SHALL$process-message
 <status value="active"/> <experimental value="false"/> <date value="2019-12-08T00:00:00-05:00"/> <publisher value="HL7 International / Pharmacy"/> <contact> <name value="HL7 International / Pharmacy"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/medication"/> </telecom> </contact> <contact> <name value="Frank McKinney"/> <telecom> <system value="email"/> <value value="fm@frankmckinney.com"/> </telecom> </contact> <description value="This CapabilityStatement describes the expected capabilities of a server that is capable of responding to a Real-time Pharmacy Benefit Check (RTPBC) request transacted with the `$process-message` operation."/> <jurisdiction> <coding> <system value="urn:iso:std:iso:3166"/> <code value="US"/> <display value="United States of America"/> </coding> </jurisdiction> <kind value="requirements"/> <fhirVersion value="4.0.1"/> <format value="xml"/> <format value="json"/> <patchFormat value="application/json-patch+json"/> <rest> <mode value="server"/> <documentation value="RTPBC Responder **SHALL**: 1. Support the $process-message operation. 2. Support at least one use case defined in this IG and listed in the Use Cases section. 3. Implement the RESTful behavior according to the FHIR specification. 4. Support the JSON source format. 5. Provide on the server a CapabilityStatement identifying the profiles supported. RTPBC Responder **SHOULD**: 1. Support the XML source format. 2. Identify the RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance."/> <security> <description value="Implementers are expected to follow core FHIR security principles (https://www.hl7.org/fhir/security.html).In addition, the FHIR Security and Privacy Module (http://hl7.org/fhir/R4/secpriv-module.html) describes how to protect patient privacy. A server **SHALL** reject any unauthorized requests by returning an `HTTP 401` unauthorized response code."/> </security> <operation> <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation"> <valueCode value="SHALL"/> </extension> <name value="process-message"/> <definition value="http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"/> </operation> </rest> </CapabilityStatement>