Consumer Real-Time Pharmacy Benefit Check FHIR IG
2.0.0 - CI Build

Consumer Real-Time Pharmacy Benefit Check FHIR IG, published by HL7 International / Pharmacy. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/carin-rtpbc/ and changes regularly. See the Directory of published versions

## CapabilityStatement: RTPBC Requester Capability Statement

Official URL: http://hl7.org/fhir/us/carin-rtpbc/CapabilityStatement/rtpbc-requester | Version: 2.0.0
Standards status: Trial-use Active as of 2019-12-08 | Maturity Level: 4 | Computable Name: RtpbcRequesterCapabilityStatement

This CapabilityStatement describes the expected capabilities of a client system submitting a Real-time Pharmacy Benefit Check (RTPBC) request using the `$process-message` operation.

### RTPBC Requester

SHALL:

- Support at least one use case defined in this Guide and listed in the Use Cases Section
- Implement the RESTful behavior according to the HL7 FHIR specification
- Support the JSON source format

SHOULD:

- Support the XML source format
- Identify the RTPBC profiles supported as part of the FHIR `meta.profile` attribute for each instance

Raw OpenAPI-Swagger Definition file | Download

Language: en

## 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.