{ "description": "EOM example for creating an mCODE-derived capability statement.", "_filename": "CapabilityStatement-eom-mcode-server.json", "package_name": "globalalliant.us.eom-updates", "format": [ "xml", "json" ], "date": "2024-01-25T14:55:00.000000-04:00", "publisher": null, "fhirVersion": "4.0.1", "name": "CapabilityStatementEomPatientBundle", "type": null, "experimental": "true", "resourceType": "CapabilityStatement", "imports": [ "http://hl7.org/fhir/us/core/CapabilityStatement/us-core-server" ], "title": "mCODE EOM Server: Get Bundle for an EOM Patient", "package_version": "1.1.0-alpha-2", "status": "draft", "id": "03fe66bf-2ba3-41c0-9b7e-285f3e319bc4", "kind": "requirements", "implementationGuide": [ "http://hl7.org/fhir/us/mcode/ImplementationGuide/hl7.fhir.us.mcode" ], "url": "https://globalalliantinc.com/enhancing-oncology-model/CapabilityStatement/eom-mcode-server", "version": null, "rest": [ { "mode": "server", "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": [ { "name": "eom-mcode-patient-bundle", "extension": [ { "url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation", "valueCode": "SHOULD" } ], "definition": "http://hl7.org/fhir/us/mcode/OperationDefinition/mcode-patient-everything" } ], "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.\n" } ] }