FHIR IG Statistics: CapabilityStatement/rtpbc-responder

Resources that use this resource

No resources found

Resources that this resource uses

No resources found

Narrative

Note: links and images are rebased to the (stated) source

Source

{
  "resourceType": "CapabilityStatement",
  "id": "rtpbc-responder",
  "text": {
    "status": "extensions",
    "div": "<!-- snip (see above) -->"
  },
  "url": "http://hl7.org/fhir/us/carin-rtpbc/CapabilityStatement/rtpbc-responder",
  "version": "1.0.0",
  "name": "RtpbcResponderCapabilityStatement",
  "title": "RTPBC Responder Capability Statement",
  "status": "active",
  "experimental": false,
  "date": "2019-12-08T00:00:00-05:00",
  "publisher": "HL7 International - Pharmacy",
  "contact": [
    {
      "name": "HL7 International - Pharmacy",
      "telecom": [
        {
          "system": "url",
          "value": "http://www.hl7.org/Special/committees/medication"
        }
      ]
    },
    {
      "name": "Frank McKinney",
      "telecom": [
        {
          "system": "email",
          "value": "frank.mckinney@pocp.com"
        }
      ]
    }
  ],
  "description": "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": "urn:iso:std:iso:3166",
          "code": "US",
          "display": "United States of America"
        }
      ]
    }
  ],
  "kind": "requirements",
  "fhirVersion": "4.0.1",
  "format": [
    "xml",
    "json"
  ],
  "patchFormat": [
    "application/json-patch+json"
  ],
  "implementationGuide": [
    "http://hl7.org/fhir/us/carin-rtpbc/ImplementationGuide/carin-rtpbc"
  ],
  "rest": [
    {
      "mode": "server",
      "documentation": "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": "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."
      },
      "operation": [
        {
          "extension": [
            {
              "url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
              "valueCode": "SHALL"
            }
          ],
          "name": "process-message",
          "definition": "http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"
        }
      ]
    }
  ]
}