HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm
2.1.1 - STU 2.1.1 United States of America flag

HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/case-reporting/ and changes regularly. See the Directory of published versions

CapabilityStatement: eCR CapabilityStatement

Official URL: http://hl7.org/fhir/us/ecr/CapabilityStatement/capabilitystatement-ecr Version: 2.1.1
Active as of 2019-06-25 Computable Name: CapabilityStatement_eCR

This resource defines the expected capabilities for both client and server participating in eCR exchange.

Raw OpenAPI-Swagger Definition file | Download

Capability Statement eCR

  • Implementation Guide Version: 2.1.1
  • FHIR Version: 4.0.1
  • Supported Formats: application/xml, application/json
  • Supported Patch Formats:
  • Published on: Tue Jun 25 00:00:00 UTC 2019
  • Published by: HL7 International / Public Health

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.

SHALL Support the Following Implementation Guides

  • http://hl7.org/fhir/us/ecr/ImplementationGuide/hl7-fhir-us-ecr

FHIR RESTful Capabilities

REST Configuration 1

Mode: server

This section describes the expected capabilities for the server participating in eCR exchange.

Summary of System-wide Interactions

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)

Resource Conformance: supportedComposition
Core FHIR Resource
Composition
Reference Policy
Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedEncounter
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedLocation
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedPatient
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedPractitionerRole
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedServiceRequest
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedBundle
Resource Conformance: supportedMessageHeader
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedPractitioner
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

REST Configuration 2

Mode: client

This section describes the expected capabilities for the client participating in eCR exchange.

Summary of System-wide Interactions

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

  • The relevant profiles (if any)
  • The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
  • The required, recommended, and some optional search parameters (if any).
  • The linked resources enabled for _include
  • The other resources enabled for _revinclude
  • The operations on the resource (if any)

Resource Conformance: supportedComposition
Core FHIR Resource
Composition
Reference Policy
Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedEncounter
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedLocation
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedPatient
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedPractitionerRole
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedServiceRequest
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedBundle
Resource Conformance: supportedMessageHeader
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.

Resource Conformance: supportedPractitioner
Profile Conformance
SHALL
Reference Policy

Interaction summary
  • Supports create, read, update, delete.