mCODE Lite (mCODE-LITE)
0.1.0 - draft

mCODE Lite (mCODE-LITE), published by MITRE. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/CodeX-HL7-FHIR-Accelerator/mcode-lite/ and changes regularly. See the Directory of published versions

CapabilityStatement: mCODE EOM Server: Get Bundle for an EOM Patient (Experimental)

Official URL: http://mitre.org/mcodelite/CapabilityStatement/eom-mcode-server Version: 0.1.0
Draft as of 2024-01-25 Computable Name: CapabilityStatementEomPatientBundle

EOM example for creating an mCODE-derived capability statement.

Raw OpenAPI-Swagger Definition file | Download

mCODE EOM Server: Get an EOM Bundle for a Patient

  • Official URL:http://hl7.org/fhir/us/mcode/CapabilityStatement/mcode-sender-patient-bundle
  • Implementation Guide Version: None
  • FHIR Version: 4.0.1
  • Intended Use: Requirements
  • Supported Formats: XML, JSON
  • Published: 2020-10-30 07:15:00.000000-04:00
  • Published by: None
  • Status: Draft (experimental)

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.

Support the Following Implementation Guides:

Include And Support Everything In The Following CapabilityStatements:

FHIR Server RESTful Capabilities

An mCODE EOM Server SHOULD:

  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 EOM 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 SHOULD reject any unauthorized requests by returning an HTTP 401 unauthorized response code.

Summary of Server Wide Operations