Patient Cost Transparency Implementation Guide
2.0.0-ballot - STU 2 Ballot 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-ballot 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.0-ballot
Standards status: Trial-use 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

Patient Cost Transparency Implementation Guide Coordination Requester Capability Statement

  • Implementation Guide Version: 2.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: SHALL support json, SHOULD support xml
  • Supported Patch Formats:
  • 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.

FHIR RESTful Capabilities

Mode: client

Summary of System-wide Interactions

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
BundleSupported profiles:
  PCT GFE Coordination Bundle
  PCT GFE Collection Bundle
  PCT GFE Information Bundle
  PCT GFE Bundle
  PCT GFE Missing Bundle
yyyyyyyyy
OrganizationSupported profiles:
  PCT Organization
yyyyyyyyy
PractitionerSupported profiles:
  PCT Practitioner
yyyyyyyyy
PractitionerRoleSupported profiles:
  HRex PractitionerRole Profile
yyyyyyyyy$GFERetrieve

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.

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.

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.

Extended Operations
ConformanceOperationDocumentation
SHALL$GFERetrieve

This operation is used by an entity to retrieve a GFE Collection Bundle 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 Collection Bundle. If the task reference is to a Coordination Task, this will return the GFE Collection Bundle. 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 Collection Bundle if the referenced task was a Coordination Task.)