Pan-Canadian eReferral-eConsult (CA:eReC)
1.2.0-DFT 
DFT - The specification is currently in development and subject to change. For a full list of available versions, see the Directory of published versions
CapabilityStatement eReC Requester L1
REST Capabilities Server
| Mode | Server |
|---|---|
| Documentation | An eReC Requester SHALL be capable of participating in the RESTful exchange of FHIR Messages in the role of server (i.e. recipient of requests), use of |
Global Operations
| Operation | Reference | Level |
|---|---|---|
| process-message | Process Message | SHALL |
REST Capabilities Client
| Mode | Client |
|---|---|
| Documentation | An eReC Requester SHALL be capable of participating in the RESTful exchange of FHIR Messages in the role of client (i.e. sender of responses to requests, notification of updates). Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.) |
Global Operations
| Operation | Reference | Level |
|---|---|---|
| process-message | Process Message | SHALL |
Messaging Capabilities
| Endpoints |
| ||||||
|---|---|---|---|---|---|---|---|
| Supported Messages |
|
| CapabilityStatement |
| id : ca-eReferral-eReCRequester-L1 |
| url : http://fhir.infoway-inforoute.ca/io/CA-eReC/CapabilityStatement/ca-eReferral-eReCRequester-L1 |
| version : 1.0.0 |
| name : eReCRequesterL1 |
| title : eReC L1 Requester |
| status : draft |
| experimental : False |
| date : 2021-07-15 |
| description : This is the FHIR capability statement for a system performing the role of eReC Level 1 Requester. |
| kind : requirements |
| fhirVersion : 4.0.1 |
| format : json |
| rest |
| mode : server |
| documentation : An eReC Requester **SHALL** be capable of participating in the RESTful exchange of FHIR Messages in the role of server (i.e. recipient of requests), use of `$process-message` endpoint / operation is recommended. Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.) |
| operation |
| extension |
| url : http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation |
| value : SHALL |
| name : process-message |
| definition : http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message |
| rest |
| mode : client |
| documentation : An eReC Requester **SHALL** be capable of participating in the RESTful exchange of FHIR Messages in the role of client (i.e. sender of responses to requests, notification of updates). Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.) |
| operation |
| extension |
| url : http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation |
| value : SHALL |
| name : process-message |
| definition : http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message |
| messaging |
| supportedMessage |
| extension |
| url : http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation |
| value : SHALL |
| mode : sender |
| definition : http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-add-service-request |
| supportedMessage |
| extension |
| url : http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation |
| value : SHALL |
| mode : sender |
| definition : http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-revoke-service-request |
<url value="http://fhir.infoway-inforoute.ca/io/CA-eReC/CapabilityStatement/ca-eReferral-eReCRequester-L1" />
<description value="This is the FHIR capability statement for a system performing the role of eReC Level 1 Requester." />
<documentation value="An eReC Requester **SHALL** be capable of participating in the RESTful exchange of FHIR Messages in the role of server (i.e. recipient of requests), use of `$process-message` endpoint / operation is recommended. Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.)" />
</extension>
</operation>
</rest>
<documentation value="An eReC Requester **SHALL** be capable of participating in the RESTful exchange of FHIR Messages in the role of client (i.e. sender of responses to requests, notification of updates). Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.)" />
</extension>
</operation>
</rest>
</extension>
<definition value="http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-add-service-request" />
</supportedMessage>
</extension>
<definition value="http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-revoke-service-request" />
</supportedMessage>
</messaging>
</CapabilityStatement>
{
"url": "http://fhir.infoway-inforoute.ca/io/CA-eReC/CapabilityStatement/ca-eReferral-eReCRequester-L1",
"description": "This is the FHIR capability statement for a system performing the role of eReC Level 1 Requester.",
"json"
],
{
"documentation": "An eReC Requester **SHALL** be capable of participating in the RESTful exchange of FHIR Messages in the role of server (i.e. recipient of requests), use of `$process-message` endpoint / operation is recommended. Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.)",
{
{
}
],
}
]
},
{
"documentation": "An eReC Requester **SHALL** be capable of participating in the RESTful exchange of FHIR Messages in the role of client (i.e. sender of responses to requests, notification of updates). Note: This CapabilityStatement provides details message level conformance requirements. (See XML or JSON view for details not visible in the summary.)",
{
{
}
],
}
]
}
],
{
{
{
}
],
"definition": "http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-add-service-request"
},
{
{
}
],
"definition": "http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-revoke-service-request"
}
]
}
]
}