Consumer Real-Time Pharmacy Benefit Check
1.0.0 - STU1

This page is part of the Consumer Real-time Pharmacy Benefit Check (v1.0.0: STU 1) based on FHIR R4. This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

: RtpbcResponderCapabilityStatement - XML Representation

Raw xml | Download


<CapabilityStatement xmlns="http://hl7.org/fhir">
  <id value="rtpbc-responder"/>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><h2>RtpbcResponderCapabilityStatement</h2><div><p>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 <code>$process-message</code> operation.</p>
</div><table><tr><td>Mode</td><td>SERVER</td></tr><tr><td>Description</td><td>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.</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-rtpbc/CapabilityStatement/rtpbc-responder"/>
  <version value="1.0.0"/>
  <name value="RtpbcResponderCapabilityStatement"/>
  <title value="RTPBC Responder Capability Statement"/>
  <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="frank.mckinney@pocp.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"/>
  <implementationGuide
                       value="http://hl7.org/fhir/us/carin-rtpbc/ImplementationGuide/carin-rtpbc"/>
  <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>