Patient Cost Transparency Implementation Guide
2.0.1 - STU 2

Patient Cost Transparency Implementation Guide, published by HL7 International / Financial Management. This guide is not an authorized publication; it is the continuous build for version 2.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/davinci-pct/ and changes regularly. See the Directory of published versions

## CapabilityStatement: Patient Cost Transparency Implementation Guide Coordination Requester Capability Statement

Official URL: http://hl7.org/fhir/us/davinci-pct/CapabilityStatement/davinci-pct-coordination-requester | Version: 2.0.1
Standards status: Trial-use | Maturity Level: 2 | Computable Name: CoordinationRequesterPatientCostTransparencyCapabilityStatement
Other Identifiers: OID:2.16.840.1.113883.4.642.40.4.13.3
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

Coordination Requester Capability Statement for the Da Vinci Patient Cost Transparency Implementation Guide

Raw OpenAPI-Swagger Definition file | Download

version: 1; Last updated: 2024-03-23 19:21:32+0000

## Patient Cost Transparency Implementation Guide Coordination Requester Capability Statement

- Implementation Guide Version: 2.0.1
- FHIR Version: 4.0.1
- Supported Formats: SHALL support `json`, SHOULD support `xml`
- Published on: 2024-03-23 14:21:32-0500
- Published by: HL7 International / Financial Management

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

This CapabilityStatement imports the CapabilityStatement US Core Server CapabilityStatementversion: 7.0.0)

## FHIR RESTful Capabilities

### REST Configuration: 1

#### Mode: `client`

#### Capabilities by Resource/Profile

##### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | V-R | S | U | P | C | D | H-I | H-T | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
Task | Supported Profiles PCT GFE Contributor Task | Y | y? | Y | Y | y? | Y | y? | y? | y? |  |  |  |
Bundle | Supported Profiles PCT GFE Coordination Bundle PCT GFE Packet PCT GFE Information Bundle PCT GFE Bundle PCT GFE Missing Bundle | Y | y? | Y | y? | y? | Y | y? | y? | y? |  |  |  |
Organization | Supported Profiles PCT Organization | Y | y? | Y | y? | y? | y? | y? | y? | y? |  |  |  |
Practitioner | Supported Profiles PCT Practitioner | Y | y? | Y | y? | y? | y? | y? | y? | y? |  |  |  |
PractitionerRole | Supported Profiles US Core PractitionerRole Profileversion: 7.0.0) | Y | y? | Y | y? | y? | y? | y? | y? | y? |  |  |  | `$GFERetrieve`

##### Resource Conformance: SHALLTask

Core FHIR Resource
Task
Reference Policy
Interaction summary

- SHALL support `create`, `search-type`, `read`, `update`.
- MAY support `vread`, `patch`, `delete`, `history-instance`, `history-type`.

Supported Profiles

PCT GFE Contributor Task

##### Resource Conformance: SHALLBundle

Core FHIR Resource
Bundle
Reference Policy
Interaction summary

- SHALL support `create`, `search-type`, `read`.
- MAY support `vread`, `update`, `patch`, `delete`, `history-instance`, `history-type`.

Supported Profiles

PCT GFE Coordination Bundle
PCT GFE Packet
PCT GFE Information Bundle
PCT GFE Bundle
PCT GFE Missing Bundle

##### Resource Conformance: SHALLOrganization

Core FHIR Resource
Organization
Reference Policy
Interaction summary

- SHALL support `search-type`, `read`.
- MAY support `create`, `vread`, `update`, `patch`, `delete`, `history-instance`, `history-type`.

Supported Profiles

PCT Organization

##### Resource Conformance: SHALLPractitioner

Core FHIR Resource
Practitioner
Reference Policy
Interaction summary

- SHALL support `search-type`, `read`.
- MAY support `create`, `vread`, `update`, `patch`, `delete`, `history-instance`, `history-type`.

Supported Profiles

PCT Practitioner

##### Resource Conformance: SHALLPractitionerRole

Core FHIR Resource
PractitionerRole
Reference Policy
Interaction summary

- SHALL support `search-type`, `read`.
- MAY support `create`, `vread`, `update`, `patch`, `delete`, `history-instance`, `history-type`.

Supported Profiles

US Core PractitionerRole Profileversion: 7.0.0)

Extended Operations

Conformance | Operation | Documentation
--- | --- | ---
SHALL | $GFERetrieve | This operation is used by an entity to retrieve a GFE Packet containing the GFE Bundle(s) and other referenced resources based on a GFE Coordination Task. The only input parameter is the single reference to the GFE Coordination Task resource. The only output is a GFE Packet. If the task reference is to a Coordination Task, this will return the GFE Packet. If this task reference is for a GFE Contributor Task, it returns the GFE Bundle, if present. If the Task reference points to a Task resource that is neither a Coordination Task or a GFE Contributor Task, the response is an HTTP error `400 - Bad Request`. If a Task is not found, the response is an HTTP error `400 - Bad Request`. If a GFE Bundle does not exist for an associated GFE Contributor Task, in place of a GFE Bundle, a GFE Missing Bundle is provided in its place (either directly ina response if the referenced task was a GFE Contributor Task or inside the GFE Packet if the referenced task was a Coordination Task.)

### REST Configuration: 2

#### Mode: `server`

#### Capabilities by Resource/Profile

##### Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

- The relevant profiles (if any)
- The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
- The required, recommended, and some optional search parameters (if any).
- The linked resources enabled for `_include`
- The other resources enabled for `_revinclude`
- The operations on the resource (if any)

Resource Type | Profile | R | V-R | S | U | P | C | D | H-I | H-T | Searches | `_include` | `_revinclude` | Operations
--- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | ---
DocumentReference | Supported Profiles PCT AEOB Packet Document Reference | Y | y? | Y |  |  |  |  | y? | y? | category, status, doc-status, type, date, patient, estimate-initiation-time, estimate-service, estimate-condition, linking-identifier, planned-period, author, relatesto |  |  |
Bundle | Supported Profiles PCT GFE Packet | Y | y? | y? | y? | y? |  | y? | y? | y? |  |  |  |

##### Resource Conformance: SHOULDDocumentReference

Core FHIR Resource
DocumentReference
Reference Policy
Interaction summary

- SHOULD support `search-type`, `read`.
- MAY support `vread`, `history-instance`, `history-type`.

Supported Profiles

PCT AEOB Packet Document Reference

Search Parameters

Conformance | Parameter | Type | Documentation
--- | --- | --- | ---
SHALL | category | `token` | Categorization of document.
SHALL | status | `token` | current | superseded | entered-in-error
SHALL | doc-status | `token` | preliminary | final | amended | entered-in-error
SHALL | type | `token` | Kind of document
SHALL | date | `date` | Kind of document
SHALL | patient | `reference` | Who/what is the subject of the document
SHOULD | estimate-initiation-time | `date` | Instant from which the request originating request was being initiated.
SHOULD | estimate-service | `token` | Significant Procedures and/or products involved in an estimate in the packet.
SHOULD | estimate-condition | `token` | Significant condition involved in an estimate in the packet.
SHOULD | linking-identifier | `token` | An identifier assigned to a particular service or series of services to enabling linking.
SHOULD | planned-period | `date` | Planned date(s) of a particular admission/service or a series of admissions/services.
SHOULD | author | `reference` | All involved authoring parties, including payer all Good Faith Estimate (GFE) providers.
SHOULD | relatesto | `reference` | Target of the relationship.

##### Resource Conformance: SHOULDBundle

Core FHIR Resource
Bundle
Reference Policy
Interaction summary

- SHOULD support `read`.
- MAY support `search-type`, `vread`, `update`, `patch`, `delete`, `history-instance`, `history-type`.

Supported Profiles

PCT GFE Packet