minimal Common Oncology Data Elements (mCODE) Implementation Guide, published by HL7 International / Clinical Interoperability Council. This guide is not an authorized publication; it is the continuous build for version 4.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/fhir-mCODE-ig/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org/fhir/us/mcode/CapabilityStatement/mcode-receiver-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.2 |
Gets an mCODE Patient Bundle for a specific patient that contains all of that patient’s resources that conform to mCODE Profiles.
Raw OpenAPI-Swagger Definition file | Download
xml
, json
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.
client
An mCODE Client SHALL:
meta.profile
attribute for each instance.The mCODE Client SHOULD:
- See the General Security Considerations section for requirements and recommendations.
- A client SHALL reject any unauthorized requests by returning an
HTTP 401
unauthorized response code.