minimal Common Oncology Data Elements (mCODE) Implementation Guide
4.0.0-ballot - STU4 Ballot United States of America flag

Publication Build: This will be filled in by the publication tooling

CapabilityStatement: mCODE Data Sender: Get Bundle for a Patient (Experimental)

Official URL: http://hl7.org/fhir/us/mcode/CapabilityStatement/mcode-sender-patient-bundle Version: 4.0.0-ballot
Draft as of 2020-10-30 Computable Name: CapabilityStatementPatientBundle
Other Identifiers: OID:2.16.840.1.113883.4.642.40.15.13.7

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.

Raw OpenAPI-Swagger Definition file | Download

mCODE Data Sender: Get Bundle for a Patient

  • Implementation Guide Version: 4.0.0-ballot
  • FHIR Version: 4.0.1
  • Supported Formats: xml, json
  • Supported Patch Formats:
  • Published on: 2020-10-30 07:15:00-0400
  • Published by: HL7 International / Clinical Interoperability Council

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.

SHALL Support the Following Implementation Guides

FHIR RESTful Capabilities

Mode: server

An mCODE Server 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 Server SHOULD:

  1. Support xml source formats for all mCODE interactions.
Security
  1. See the General Security Considerations section for requirements and recommendations.
  2. A server SHALL reject any unauthorized requests by returning an HTTP 401 unauthorized response code.
Summary of System-wide Interactions