CapabilityStatement-mcode-receiver-cancer-conditions-then-patients

Sourcehl7.fhir.us.mcode#current:minimal Common Oncology Data Elements (mCODE) Implementation Guide (v4.0.1)
resourceTypeCapabilityStatement
idmcode-receiver-cancer-conditions-then-patients
canonicalhttp://hl7.org/fhir/us/mcode/CapabilityStatement/mcode-receiver-cancer-conditions-then-patients
version3.0.0
statusdraft
publisherHL7 International Clinical Interoperability Council
nameCapabilityStatementReceiverConditionsThenPatients
titlemCODE Data Receiver: Get Conditions then Patients
date2020-10-30T07:15:00.000000-04:00
experimentaltrue
descriptionRetrieves a Bundle of Condition resources with a code in mCODE's cancer condition value set, and allows for associated Patient resources to be retrieved in a subsequent request. Use ONLY when reverse chaining AND `_include` are not available on the system.
jurisdictionsus
kindrequirements
fhirVersion4.0.1
importshttp://hl7.org/fhir/us/core/CapabilityStatement/us-core-client
formatsxml json
implementationGuideshttp://hl7.org/fhir/us/mcode/ImplementationGuide/hl7.fhir.us.mcode
Usages(none)

CapabilityStatementReceiverConditionsThenPatients

Retrieves a Bundle of Condition resources with a code in mCODE's cancer condition value set, and allows for associated Patient resources to be retrieved in a subsequent request. Use ONLY when reverse chaining AND _include are not available on the system.

Mode CLIENT
Description

An mCODE Client SHALL :

  1. Support all profiles defined in this Implementation Guide..
  2. Implement the RESTful behavior according to the FHIR specification.
  3. Return the following response classes:
    • (Status 400): invalid parameter
    • (Status 401/4xx): unauthorized request
    • (Status 403): insufficient scope
    • (Status 404): unknown resource
    • (Status 410): deleted resource.
  4. Support json source formats for all mCODE interactions.
  5. Identify the mCODE profiles supported as part of the FHIR meta.profile attribute for each instance.
  6. Support the searchParameters on each profile individually and in combination.

The mCODE Client SHOULD :

  1. Support xml source formats for all mCODE interactions.
Transaction
System History
System Search
Resource Type Profile Read Search Update Create
Patient Supported profiles:
   Cancer Patient Profile 		y
Condition Supported profiles:
   Cancer Patient Profile 		y
Group   y

Produced 08 Sep 2023