| Package | globalalliant.us.eom |
| Type | CapabilityStatement |
| Id | eom-mcode-server |
| FHIR Version | R4 |
| Source | https://globalalliantinc.com/enhancing-oncology-model/https://simplifier.net/resolve?scope=globalalliant.us.eom@1.0.1-rc2&canonical=https://globalalliantinc.com/enhancing-oncology-model/CapabilityStatement/eom-mcode-server |
| URL | https://globalalliantinc.com/enhancing-oncology-model/CapabilityStatement/eom-mcode-server |
| Status | draft |
| Date | 2024-01-25T14:55:00.000000-04:00 |
| Name | CapabilityStatementEomPatientBundle |
| Title | mCODE EOM Server: Get Bundle for an EOM Patient |
| Description | EOM example for creating an mCODE-derived capability statement. |
| Kind | requirements |
No resources found
| CapabilityStatement | |
| us-core-server | US Core Server CapabilityStatement |
| ImplementationGuide | |
| hl7.fhir.us.mcode | minimal Common Oncology Data Elements (mCODE) Implementation Guide |
| OperationDefinition | |
| mcode-patient-everything | Fetch mCODE Patient Bundle for a given Patient |
Note: links and images are rebased to the (stated) source
FHIRhttp://hl7.org/fhir/us/mcode/CapabilityStatement/mcode-sender-patient-bundleRetrieves 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.
An mCODE EOM Server SHOULD:
meta.profile attribute for each instance.The mCODE EOM Server SHOULD:
Security:
HTTP 401 unauthorized response code.Summary of Server Wide Operations
$mcode-patient-bundle operation.{
"resourceType": "CapabilityStatement",
"id": "eom-mcode-server",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"url": "https://globalalliantinc.com/enhancing-oncology-model/CapabilityStatement/eom-mcode-server",
"name": "CapabilityStatementEomPatientBundle",
"title": "mCODE EOM Server: Get Bundle for an EOM Patient",
"status": "draft",
"experimental": true,
"date": "2024-01-25T14:55:00.000000-04:00",
"description": "EOM example for creating an mCODE-derived capability statement.",
"kind": "requirements",
"imports": [
"http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server"
],
"fhirVersion": "4.0.1",
"format": [
"xml",
"json"
],
"implementationGuide": [
"http://hl7.org/fhir/us/mcode/ImplementationGuide/hl7.fhir.us.mcode"
],
"rest": [
{
"mode": "server",
"documentation": "An mCODE Enhancing Oncology Model (EOM) Server **SHOULD**:\n\n1. Support all profiles defined in this Implementation Guide..\n1. Implement the RESTful behavior according to the FHIR specification.\n1. Return the following response classes:\n - (Status 400): invalid parameter\n - (Status 401/4xx): unauthorized request\n - (Status 403): insufficient scope\n - (Status 404): unknown resource\n - (Status 410): deleted resource.\n1. Support json source formats for all mCODE interactions.\n1. Identify the mCODE profiles supported as part of the FHIR `meta.profile` attribute for each instance.\n1. Support the searchParameters on each profile individually and in combination.\n\nThe mCODE EOM Server **SHOULD**:\n\n1. Support xml source formats for all mCODE interactions.",
"security": {
"description": "1. See the [General Security Considerations](https://www.hl7.org/fhir/security.html#general) section for requirements and recommendations.\n1. A server **SHOULD** reject any unauthorized requests by returning an `HTTP 401` unauthorized response code."
},
"operation": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode": "SHOULD"
}
],
"name": "eom-mcode-patient-bundle",
"definition": "http://hl7.org/fhir/us/mcode/OperationDefinition/mcode-patient-everything"
}
]
}
]
}