This page is part of the Consumer Real-time Pharmacy Benefit Check (v0.1.0: STU 1 Ballot 1) based on FHIR R4. The current version which supercedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

• Content
• XML
• JSON

XML Format: CapabilityStatement-carin-rtpbc-responder-capabilitystatement

Raw xml

<CapabilityStatement xmlns="http://hl7.org/fhir">
  <id value="carin-rtpbc-responder-capabilitystatement"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><h2>CarinRtpbcResponderCapabilityStatement</h2><div><p>This CapabilityStatement describes the expected capabilities of a server that is capable of responding to a CARIN Real-time Pharmacy Benefit Check (RTPBC) request transacted with the <code>$process-message</code> operation.</p>
</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td>CARIN RTPBC Responder **SHALL**:   1. Support at least one use case defined in this Guide and listed in the [Use Cases](Use_cases.html) Section. 1. Implement the RESTful behavior according to the FHIR specification. 1. Support the json source format. 1. Declare a CapabilityStatement identifying the profiles supported.   CARIN RTPBC Responder **SHOULD**:   1. Support the xml source format. 1. Identify the CARIN RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance.</td></tr><tr><td>Transaction</td><td></td></tr><tr><td>System History</td><td></td></tr><tr><td>System Search</td><td></td></tr></table><table><tr><th><b>Resource Type</b></th><th><b>Profile</b></th><th><b title="GET a resource (read interaction)">Read</b></th><th><b title="GET all set of resources of the type (search interaction)">Search</b></th><th><b title="PUT a new resource version (update interaction)">Update</b></th><th><b title="POST a new resource (create interaction)">Create</b></th></tr></table></div>
  </text>
  <url value="http://hl7.org/fhir/us/carin/CapabilityStatement/rtpbc-responder"/>
  <version value="0.1.0"/>
  <name value="CarinRtpbcResponderCapabilityStatement"/>
  <title value="CARIN RTPBC Responder Capability Statement"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2019-12-08T05:00:00+00:00"/>
  <publisher value="CARIN Alliance"/>
  <description
               value="This CapabilityStatement describes the expected capabilities of a server that is capable of responding to a CARIN 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.0"/>
  <format value="xml"/>
  <format value="json"/>
  <patchFormat value="application/json-patch+json"/>
  <implementationGuide
                       value="http://hl7.org/fhir/us/carin/ImplementationGuide/carin-rtpbc"/>
  <rest>
    <mode value="server"/>
    <documentation
                   value="CARIN RTPBC Responder **SHALL**:   1. Support at least one use case defined in this Guide and listed in the [Use Cases](Use_cases.html) Section. 1. Implement the RESTful behavior according to the FHIR specification. 1. Support the json source format. 1. Declare a CapabilityStatement identifying the profiles supported.   CARIN RTPBC Responder **SHOULD**:   1. Support the xml source format. 1. Identify the CARIN RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance."/>
    <security>
      <description
                   value="1. For general security consideration refer to the [Security and Privacy Considerations](http://build.fhir.org/secpriv-module.html). 1. For security considerations specific to this guide refer to the [US Core Implementation Guide’s General Security Considerations page](http://hl7.org/fhir/us/core/security.html) for requirements and recommendations. 1. 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>