CapabilityStatement-mcode-receiver-patient-bundle

Sourcehl7.fhir.us.mcode#current:minimal Common Oncology Data Elements (mCODE) Implementation Guide (v4.0.1)
resourceTypeCapabilityStatement
idmcode-receiver-patient-bundle
canonicalhttp://hl7.org/fhir/us/mcode/CapabilityStatement/mcode-receiver-patient-bundle
version3.0.0
statusdraft
publisherHL7 International Clinical Interoperability Council
nameCapabilityStatementPatientBundle
titlemCODE Data Receiver: Get Bundle for a Patient
date2020-10-30T07:15:00.000000-04:00
experimentaltrue
descriptionGets an [mCODE Patient Bundle](StructureDefinition-mcode-patient-bundle.html) for a specific patient that contains all of that patient's resources that conform to mCODE Profiles.
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)

CapabilityStatementPatientBundle

Gets an mCODE Patient Bundle for a specific patient that contains all of that patient's resources that conform to mCODE Profiles.

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

Produced 08 Sep 2023