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
JSON Format: CapabilityStatement-carin-rtpbc-responder-capabilitystatement
Raw json
{ "resourceType" : "CapabilityStatement", "id" : "carin-rtpbc-responder-capabilitystatement", "text" : { "status" : "generated", "div" : "<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>\n</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>" }, "url" : "http://hl7.org/fhir/us/carin/CapabilityStatement/rtpbc-responder", "version" : "0.1.0", "name" : "CarinRtpbcResponderCapabilityStatement", "title" : "CARIN RTPBC Responder Capability Statement", "status" : "active", "experimental" : false, "date" : "2019-12-08T05:00:00+00:00", "publisher" : "CARIN Alliance", "description" : "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" : "urn:iso:std:iso:3166", "code" : "US", "display" : "United States of America" } ] } ], "kind" : "requirements", "fhirVersion" : "4.0.0", "format" : [ "xml", "json" ], "patchFormat" : [ "application/json-patch+json" ], "implementationGuide" : [ "http://hl7.org/fhir/us/carin/ImplementationGuide/carin-rtpbc" ], "rest" : [ { "mode" : "server", "documentation" : "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" : "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." }, "operation" : [ { "extension" : [ { "url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation", "valueCode" : "SHALL" } ], "name" : "process-message", "definition" : "http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message" } ] } ] }