Package | hl7.fhir.us.carin-rtpbc |
Resource Type | CapabilityStatement |
Id | rtpbc-requester |
FHIR Version | R4 |
Source | http://hl7.org/fhir/us/carin-rtpbc/https://build.fhir.org/ig/HL7/carin-rtpbc/CapabilityStatement-rtpbc-requester.html |
URL | http://hl7.org/fhir/us/carin-rtpbc/CapabilityStatement/rtpbc-requester |
Version | 2.0.0 |
Status | active |
Date | 2019-12-08T00:00:00-05:00 |
Name | RtpbcRequesterCapabilityStatement |
Title | RTPBC Requester Capability Statement |
Realm | us |
Authority | hl7 |
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. |
Kind | requirements |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Generated Narrative: CapabilityStatement rtpbc-requester
xml
, json
application/json-patch+json
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.
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.
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.
{ "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." } } ] }