HL7 FHIR® Implementation Guide: Electronic Case Reporting (eCR) - US Realm
1.1.0 - STU 2 Ballot

This page is part of the electronic Case Reporting (eCR) (v1.1.0: STU 2 on FHIR R4 Ballot 1) based on FHIR R4. The current version which supercedes this version is 2.1.0. For a full list of available versions, see the Directory of published versions

CapabilityStatement: eCR CapabilityStatement

Raw OpenAPI-Swagger Definition file | Download

id capabilitystatement-ecr
url http://hl7.org/fhir/us/ecr/CapabilityStatement/capabilitystatement-ecr
version 1.0.0
name CapabilityStatement_eCR
title Capability Statement eCR
status active
experimental false
date 2019-06-25
publisher HL7 Public Health Work Group
description

This resource defines the expected capabilities for both client and server participating in eCR exchange
kind requirements
fhirVersion 4.0.1
format xml
format json
implementationGuide http://hl7.org/fhir/us/ecr/ImplementationGuide/hl7-fhir-us-ecr
rest
mode server
resource
type Composition
profile http://hl7.org/fhir/us/ecr/StructureDefinition/eicr-composition
documentation Defines a set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. The Composition resource provides the basic structure of a FHIR document. The full content of the document is expressed using a Bundle containing the Composition and its entries.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Communication
profile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication
documentation This resource is a record of a communication even if it is planned or has failed. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, or devices.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-responsible-agency-organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-rules-authoring-agency-organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-routing-entity-organization
documentation This resource may be used in a shared registry of contact and other information for various organizations or it can be used merely as a support for other resources that need to reference organizations, perhaps as a document, message or as a contained resource.
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
resource
type Encounter
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-encounter
documentation An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Location
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-location
documentation Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
resource
type Observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/travel-history-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/pregnancy-outcome-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/pregnancy-status-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/last-menstrual-period
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/postpartum-status
documentation Observation allows expressing a name-value pair or structured collection of name-value pairs.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type PlanDefinition
profile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-relevant-reportable-condition-plandefinition
documentation This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. A plan definition is a pre-defined group of actions to be taken in particular circumstances, often including conditional elements, options, and other decision points.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Patient
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-patient
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
resource
type PractitionerRole
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-practitionerrole
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
rest
mode client
resource
type Composition
profile http://hl7.org/fhir/us/ecr/StructureDefinition/eicr-composition
documentation Defines a set of healthcare-related information that is assembled together into a single logical document that provides a single coherent statement of meaning, establishes its own context and that has clinical attestation with regard to who is making the statement. The Composition resource provides the basic structure of a FHIR document. The full content of the document is expressed using a Bundle containing the Composition and its entries.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Communication
profile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-communication
documentation This resource is a record of a communication even if it is planned or has failed. A communication is a conveyance of information from one entity, a sender, to another entity, a receiver. The sender and receivers may be patients, practitioners, related persons, organizations, or devices.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-responsible-agency-organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-rules-authoring-agency-organization
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-routing-entity-organization
documentation This resource may be used in a shared registry of contact and other information for various organizations or it can be used merely as a support for other resources that need to reference organizations, perhaps as a document, message or as a contained resource.
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
resource
type Encounter
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-encounter
documentation An interaction between a patient and healthcare provider(s) for the purpose of providing healthcare service(s) or assessing the health status of a patient.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Location
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-location
documentation Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained, or accommodated.
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
resource
type Observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/travel-history-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-reason-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-eicr-processing-status-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/pregnancy-outcome-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/pregnancy-status-observation
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/last-menstrual-period
supportedProfile http://hl7.org/fhir/us/ecr/StructureDefinition/postpartum-status
documentation Observation allows expressing a name-value pair or structured collection of name-value pairs.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type PlanDefinition
profile http://hl7.org/fhir/us/ecr/StructureDefinition/rr-relevant-reportable-condition-plandefinition
documentation This resource allows for the definition of various types of plans as a sharable, consumable, and executable artifact. The resource is general enough to support the description of a broad range of clinical artifacts such as clinical decision support rules, order sets and protocols. A plan definition is a pre-defined group of actions to be taken in particular circumstances, often including conditional elements, options, and other decision points.
interaction
capabilitystatement-expectation
  • SHALL
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • SHOULD
code delete
resource
type Patient
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-patient
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete
resource
type PractitionerRole
profile http://hl7.org/fhir/us/ecr/StructureDefinition/us-ph-practitionerrole
interaction
capabilitystatement-expectation
  • SHOULD
code create
interaction
capabilitystatement-expectation
  • SHALL
code read
interaction
capabilitystatement-expectation
  • SHOULD
code update
interaction
capabilitystatement-expectation
  • MAY
code delete