FHIR © HL7.org  |  Server Home  |  XIG Home  |  XIG Stats  |  Server Source  |  FHIR  

FHIR IG Statistics: CapabilityStatement/rtpbc-requester

Packagehl7.fhir.us.carin-rtpbc
Resource TypeCapabilityStatement
Idrtpbc-requester
FHIR VersionR4
Sourcehttp://hl7.org/fhir/us/carin-rtpbc/https://build.fhir.org/ig/HL7/carin-rtpbc/CapabilityStatement-rtpbc-requester.html
URLhttp://hl7.org/fhir/us/carin-rtpbc/CapabilityStatement/rtpbc-requester
Version2.0.0
Statusactive
Date2019-12-08T00:00:00-05:00
NameRtpbcRequesterCapabilityStatement
TitleRTPBC Requester Capability Statement
Realmus
Authorityhl7
DescriptionThis CapabilityStatement describes the expected capabilities of a client system submitting a Real-time Pharmacy Benefit Check (RTPBC) request using the `$process-message` operation.
Kindrequirements

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

Generated Narrative: CapabilityStatement rtpbc-requester

RTPBC Requester Capability Statement

  • Implementation Guide Version: 2.0.0
  • 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 Requester SHALL: 1. Support at least one use case defined in this IG and listed in the Use Cases section. 2. Implement the RESTful behavior according to the FHIR specification. 3. Support the JSON source format. RTPBC Requester 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.

Summary of System-wide Interactions

Source

{
  "resourceType": "CapabilityStatement",
  "id": "rtpbc-requester",
  "text": {
    "status": "extensions",
    "div": "<!-- snip (see above) -->"
  },
  "extension": [
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
      "valueCode": "phx"
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
      "valueInteger": 4,
      "_valueInteger": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/us/carin-rtpbc/ImplementationGuide/hl7.fhir.us.carin-rtpbc"
          }
        ]
      }
    },
    {
      "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
      "valueCode": "trial-use",
      "_valueCode": {
        "extension": [
          {
            "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
            "valueCanonical": "http://hl7.org/fhir/us/carin-rtpbc/ImplementationGuide/hl7.fhir.us.carin-rtpbc"
          }
        ]
      }
    }
  ],
  "url": "http://hl7.org/fhir/us/carin-rtpbc/CapabilityStatement/rtpbc-requester",
  "version": "2.0.0",
  "name": "RtpbcRequesterCapabilityStatement",
  "title": "RTPBC Requester 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": "fm@frankmckinney.com"
        }
      ]
    }
  ],
  "description": "This CapabilityStatement describes the expected capabilities of a client system submitting a Real-time Pharmacy Benefit Check (RTPBC) request using 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"
  ],
  "rest": [
    {
      "mode": "server",
      "documentation": "RTPBC Requester **SHALL**: 1. Support at least one use case defined in this IG and listed in the Use Cases section. 2. Implement the RESTful behavior according to the FHIR specification. 3. Support the JSON source format.  RTPBC Requester **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."
      }
    }
  ]
}