Patient Cost Transparency Implementation Guide
2.0.0 - STU 2 United States of America flag

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.0 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 Payer Capability Statement

Official URL: http://hl7.org/fhir/us/davinci-pct/CapabilityStatement/davinci-pct Version: 2.0.0
Standards status: Trial-use Maturity Level: 2 Computable Name: PatientCostTransparencyCapabilityStatement
Other Identifiers: OID:2.16.840.1.113883.4.642.40.4.13.1

Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

Payer capability statement for the Da Vinci Patient Cost Transparency Implementation Guide

Raw OpenAPI-Swagger Definition file | Download

version: 1; Last updated: 2023-03-28 19:21:32+0000

Patient Cost Transparency Implementation Guide Payer Capability Statement

  • Implementation Guide Version: 2.0.0
  • FHIR Version: 4.0.1
  • Supported Formats: SHALL support json, SHOULD support xml
  • Published on: 2023-03-28 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: null7.0.0)

FHIR RESTful Capabilities

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 TypeProfileRV-RSUPCDH-IH-TSearches_include_revincludeOperations
DocumentReferenceSupported Profiles
  PCT AEOB Packet Document Reference
  PCT GFE Bundle
  PCT GFE Packet
Yy?Yy?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$GFESubmit
ExplanationOfBenefitSupported Profiles
  PCT Advanced EOB
Yy?Yy?y?y?y?y?y?
CoverageSupported Profiles
  PCT Coverage
Yy?Yy?y?y?y?y?y?
ClaimSupported Profiles
  PCT Good Faith Estimate Professional
  PCT Good Faith Estimate Institutional
Yy?Yy?y?y?y?y?y?
OrganizationSupported Profiles
  PCT Organization
Yy?Yy?y?y?y?y?y?
PractitionerSupported Profiles
  PCT Practitioner
Yy?Yy?y?y?y?y?y?

Resource Conformance: SHOULD DocumentReference

Core FHIR Resource
DocumentReference
Reference Policy
Interaction summary
  • SHOULD support search-type, read.
  • MAY support vread, history-instance, history-type, patch, delete, history-instance, history-type.

Search Parameters
ConformanceParameterTypeDocumentation
SHALLcategorytoken

Categorization of document.

SHALLstatustoken

current | superseded | entered-in-error

SHALLdoc-statustoken

preliminary | final | amended | entered-in-error

SHALLtypetoken

Kind of document

SHALLdatedate

Kind of document

SHALLpatientreference

Who/what is the subject of the document

SHOULDestimate-initiation-timedate

Instant from which the request originating request was being initiated.

SHOULDestimate-servicetoken

Significant Procedures and/or products involved in an estimate in the packet.

SHOULDestimate-conditiontoken

Significant condition involved in an estimate in the packet.

SHOULDlinking-identifiertoken

An identifier assigned to a particular service or series of services to enabling linking.

SHOULDplanned-perioddate

Planned date(s) of a particular admission/service or a series of admissions/services.

SHOULDauthorreference

All involved authoring parties, including payer all Good Faith Estimate (GFE) providers.

SHOULDrelatestoreference

Target of the relationship.

 
Extended Operations
ConformanceOperationDocumentation
SHALL$GFESubmit

This operation is used by an entity to submit one or multiple GFEs as a Bundle containing the GFE(s) and other referenced resources for processing. The only input parameter is the single Bundle resource with one or multiple GFE(s) - each of which is based on the Claim resource (along with other referenced resources). The only output is a url for subsequent polling per async pattern. If after polling the response is complete, then the result will either be a single Bundle with the AEOB - which is based on the ExplanationOfBenefit resource, (and other referenced resources) or an OperationOutcome resource indicating the AEOB will be sent directly to the patient.

Resource Conformance: SHOULD ExplanationOfBenefit

Core FHIR Resource
ExplanationOfBenefit
Reference Policy
Interaction summary
  • SHALL support search-type, read.
  • MAY support create, vread, update, patch, delete, history-instance, history-type.

Supported Profiles

PCT Advanced EOB

Resource Conformance: SHOULD Coverage

Core FHIR Resource
Coverage
Reference Policy
Interaction summary
  • SHALL support search-type, read.
  • MAY support create, vread, update, patch, delete, history-instance, history-type.

Supported Profiles

PCT Coverage

Resource Conformance: SHOULD Claim

Core FHIR Resource
Claim
Reference Policy
Interaction summary
  • SHALL support search-type, read.
  • MAY support create, vread, update, patch, delete, history-instance, history-type.

Resource Conformance: SHOULD Organization

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: SHOULD Practitioner

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