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

  • Title:Patient Cost Transparency Implementation Guide Coordination Requester Capability Statement
  • Implementation Guide Version: 2.0.0-ballot
  • FHIR Version: 4.0.1
  • Intended Use: Requirements
  • Supported Formats: SHALL support json; SHOULD support xml;
  • Published: 2024-03-23 14:21:32-0500
  • Published by: HL7 International / Financial Management
  • Status: Active
  • Copyright:

    Used by permission of HL7 International, all rights reserved Creative Commons License


Description:

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


Support and Requirements for Other Artifacts

Imports other capabilities:

Jump to:


FHIR Client RESTful Capabilities

System-wide Client Capabilities

Summary of Resource/Profile Capabilities

♦ = SHALL expectation; ⋄ = SHOULD expectation; ▿ = MAY expectation;

Resource Type Supported Interactions Supported Profiles Supported Searches Supported _includes Supported _revincludes Supported Operations
Bundle create♦, search-type♦, read♦, vread▿, update▿, patch▿, delete▿, history-instance▿, history-type▿, PCT GFE Coordination Bundle, PCT GFE Collection Bundle, PCT GFE Information Bundle, PCT GFE Bundle, PCT GFE Missing Bundle,
Organization create▿, search-type♦, read♦, vread▿, update▿, patch▿, delete▿, history-instance▿, history-type▿, PCT Organization♦,
Practitioner create▿, search-type♦, read♦, vread▿, update▿, patch▿, delete▿, history-instance▿, history-type▿, PCT Practitioner♦,
PractitionerRole create▿, search-type♦, read♦, vread▿, update▿, patch▿, delete▿, history-instance▿, history-type▿, HRex PractitionerRole Profile♦, $GFERetrieve♦

RESTful Client Capabilities by Resource/Profile:

Bundle

Conformance Expectation:

Supported Profiles:


Modify Criteria:

  • A Client SHALL be capable of a create interaction posting a Bundle resource using: POST [base]/Bundle/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing Bundle resource using: PUT [base]/Bundle/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Bundle resource using: PATCH [base]/Bundle/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Bundle resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHALL be capable of a search-type interaction fetching Bundle resources matching a search query using: GET [base]/Bundle/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHALL be capable of a read interaction fetching a Bundle resource using: GET [base]/Bundle/[id]
  • A Client MAY be capable of a vread interaction fetching a Bundle resource using: GET [base]/Bundle/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Bundle using: GET [base]/Bundle/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Bundle resources using: GET [base]/Bundle/_history{?[parameters]&_format=[mime-type]}

Organization

Conformance Expectation:

Supported Profiles:


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a Organization resource using: POST [base]/Organization/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing Organization resource using: PUT [base]/Organization/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Organization resource using: PATCH [base]/Organization/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Organization resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHALL be capable of a search-type interaction fetching Organization resources matching a search query using: GET [base]/Organization/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHALL be capable of a read interaction fetching a Organization resource using: GET [base]/Organization/[id]
  • A Client MAY be capable of a vread interaction fetching a Organization resource using: GET [base]/Organization/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Organization using: GET [base]/Organization/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Organization resources using: GET [base]/Organization/_history{?[parameters]&_format=[mime-type]}

Practitioner

Conformance Expectation:

Supported Profiles:


Modify Criteria:

  • A Client MAY be capable of a create interaction posting a Practitioner resource using: POST [base]/Practitioner/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing Practitioner resource using: PUT [base]/Practitioner/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing Practitioner resource using: PATCH [base]/Practitioner/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a Practitioner resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHALL be capable of a search-type interaction fetching Practitioner resources matching a search query using: GET [base]/Practitioner/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHALL be capable of a read interaction fetching a Practitioner resource using: GET [base]/Practitioner/[id]
  • A Client MAY be capable of a vread interaction fetching a Practitioner resource using: GET [base]/Practitioner/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a Practitioner using: GET [base]/Practitioner/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of Practitioner resources using: GET [base]/Practitioner/_history{?[parameters]&_format=[mime-type]}

PractitionerRole

Conformance Expectation:

Supported Profiles:

PractitionerRole Interaction Summary:

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

Modify Criteria:

  • A Client MAY be capable of a create interaction posting a PractitionerRole resource using: POST [base]/PractitionerRole/[id]{?_format=[mime-type]}
  • A Client MAY be capable of putting a existing PractitionerRole resource using: PUT [base]/PractitionerRole/[id]{?_format=[mime-type]}
  • A Client MAY be capable of patching an existing PractitionerRole resource using: PATCH [base]/PractitionerRole/[id]{?_format=[mime-type]}
  • A Client MAY be capable of deleting a PractitionerRole resource using: DELETE [base]//[id]

Fetch and Search Criteria:

  • A Client SHALL be capable of a search-type interaction fetching PractitionerRole resources matching a search query using: GET [base]/PractitionerRole/[id]{?[parameters]{&_format=[mime-type]}}
  • A Client SHALL be capable of a read interaction fetching a PractitionerRole resource using: GET [base]/PractitionerRole/[id]
  • A Client MAY be capable of a vread interaction fetching a PractitionerRole resource using: GET [base]/PractitionerRole/[id]/_history/vid
  • A Client MAY be capable of a history-instance interaction fetching a history of a PractitionerRole using: GET [base]/PractitionerRole/[id]/_history{?[parameters]&_format=[mime-type]}
  • A Client MAY be capable of a history-type interaction fetching the history of PractitionerRole resources using: GET [base]/PractitionerRole/_history{?[parameters]&_format=[mime-type]}