Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC) v1.1.0-DFT-Ballot

1.1.0-DFT-Ballot   Canada flag
  • Index
  • Home
  • Business Context
    • Business Models
    • Use Cases
    • Business Events
    • Business Rules
    • Privacy and Security Guidance
    • Provincial Considerations
  • Technical Context
    • Technical Foundation
    • Integration Patterns
    • Messaging
    • Sequence Diagrams
    • Conformance Requirements
  • FHIR Artifacts
    • Messaging Events
    • Resource Profiles
    • Extensions
    • Terminology
    • Examples
    • Capability Statements
    • Downloads
    • ---
    • Appointment (CA:eReC)
    • Bundle (CA:eReC)
    • Communication (CA:eReC)
    • DocumentReference (CA:eReC)
    • Location (CA:eReC)
    • MessageHeader (CA:eReC)
    • Organization (CA:eReC)
    • Patient (CA:eReC)
    • Practitioner (CA:eReC)
    • PractitionerRole (CA:eReC)
    • HealthcareService (CA:eReC)
    • QuestionnaireResponse (CA:eReC)
    • ServiceRequest (CA:eReC)
    • Task (CA:eReC)
  • Change Log
    1. Index
    2. FHIR Artifacts
    3. Capability Statements
    4. CapabilityStatement eReC Recipient L3

preBallot - The specification is currently in ballot review and subject to change. . . . For a full list of available versions, see the Directory of published versions

CapabilityStatement eReC Recipient L3

  • Overview
  • Tree view
  • XML
  • JSON

REST Capabilities Server

ModeServer
Documentation

An eReC Recipient 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.)

Resource Interactions

Resource Type

Global Operations

OperationReferenceLevel
process-messageProcess MessageSHOULD

REST Capabilities Client

ModeClient
Documentation

An eReC Recipient 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.)

Resource Interactions

Resource Type

Global Operations

OperationReferenceLevel
process-messageProcess MessageSHALL

Messaging Capabilities

ProtocolAddress
ModeSupported Message
Receiverhttp://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-add-service-record
Receiverhttp://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-update-service-record
CapabilityStatement
id : ca-eReferral-eReCRecipient
url : http://fhir.infoway-inforoute.ca/io/CA-eReC/CapabilityStatement/ca-eReferral-eReCRecipient
version : 1.0.0
name : eReCRecipient
title : eReC Recipient
status : draft
experimental : False
date : 2021-07-15
description : This is the FHIR capability statement for a system performing the role of eReC Recipient.
kind : requirements
fhirVersion : 4.0.1
format : json
rest
mode : server
documentation : An eReC Recipient **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 : SHOULD
name : process-message
definition : http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message
rest
mode : client
documentation : An eReC Recipient **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 : SHOULD
mode : receiver
definition : http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-add-service-record
supportedMessage
extension
url : http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation
value : SHOULD
mode : receiver
definition : http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-update-service-record
<CapabilityStatement xmlns="http://hl7.org/fhir">
    <id value="ca-eReferral-eReCRecipient" />
    <url value="http://fhir.infoway-inforoute.ca/io/CA-eReC/CapabilityStatement/ca-eReferral-eReCRecipient" />
    <version value="1.0.0" />
    <name value="eReCRecipient" />
    <title value="eReC Recipient" />
    <status value="draft" />
    <experimental value="false" />
    <date value="2021-07-15" />
    <description value="This is the FHIR capability statement for a system performing the role of eReC Recipient." />
    <kind value="requirements" />
    <fhirVersion value="4.0.1" />
    <format value="json" />
    <rest>
        <mode value="server" />
        <documentation value="An eReC Recipient **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">
                <valueCode value="SHOULD" />
            </extension>
            <name value="process-message" />
            <definition value="http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message" />
        </operation>
    </rest>
    <rest>
        <mode value="client" />
        <documentation value="An eReC Recipient **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">
                <valueCode value="SHALL" />
            </extension>
            <name value="process-message" />
            <definition value="http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message" />
        </operation>
    </rest>
    <messaging>
        <supportedMessage>
            <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
                <valueCode value="SHOULD" />
            </extension>
            <mode value="receiver" />
            <definition value="http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-add-service-record" />
        </supportedMessage>
        <supportedMessage>
            <extension url="http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation">
                <valueCode value="SHOULD" />
            </extension>
            <mode value="receiver" />
            <definition value="http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-update-service-record" />
        </supportedMessage>
    </messaging>
</CapabilityStatement>
{
    "resourceType": "CapabilityStatement",
    "id": "ca-eReferral-eReCRecipient",
    "url": "http://fhir.infoway-inforoute.ca/io/CA-eReC/CapabilityStatement/ca-eReferral-eReCRecipient",
    "version": "1.0.0",
    "name": "eReCRecipient",
    "title": "eReC Recipient",
    "status": "draft",
    "experimental": false,
    "date": "2021-07-15",
    "description": "This is the FHIR capability statement for a system performing the role of eReC Recipient.",
    "kind": "requirements",
    "fhirVersion": "4.0.1",
    "format":  [
        "json"
    ],
    "rest":  [
        {
            "mode": "server",
            "documentation": "An eReC Recipient **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",
                            "valueCode": "SHOULD"
                        }
                    ],
                    "name": "process-message",
                    "definition": "http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"
                }
            ]
        },
        {
            "mode": "client",
            "documentation": "An eReC Recipient **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",
                            "valueCode": "SHALL"
                        }
                    ],
                    "name": "process-message",
                    "definition": "http://hl7.org/fhir/OperationDefinition/MessageHeader-process-message"
                }
            ]
        }
    ],
    "messaging":  [
        {
            "supportedMessage":  [
                {
                    "extension":  [
                        {
                            "url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                            "valueCode": "SHOULD"
                        }
                    ],
                    "mode": "receiver",
                    "definition": "http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-add-service-record"
                },
                {
                    "extension":  [
                        {
                            "url": "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
                            "valueCode": "SHOULD"
                        }
                    ],
                    "mode": "receiver",
                    "definition": "http://fhir.infoway-inforoute.ca/io/CA-eReC/MessageDefinition/ca-ereferral-notify-update-service-record"
                }
            ]
        }
    ]
}

Table of Contents | IG © based on FHIR R4 | Package package:ca.infoway.io.erec@1.1.1-dft-ballot | Version History
HL7® and FHIR® are the registered trademarks of Health Level Seven International