Central Cancer Registry Reporting Content IG
1.0.0 - STU 1 United States of America flag

Central Cancer Registry Reporting Content IG, published by HL7 International / Public Health. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-central-cancer-registry-reporting-ig/ and changes regularly. See the Directory of published versions

CapabilityStatement: Central Cancer Registry Reporting EHR Capability Statement

Official URL: http://hl7.org/fhir/us/central-cancer-registry-reporting/CapabilityStatement/central-cancer-registry-reporting-ehr Version: 1.0.0
Draft as of 2020-12-06 Computable Name: CentralCancerRegistryReportingEHRCapabilityStatement

This profile defines the expected capabilities of the ‘‘EHR’’ actor when conforming to the Central Cancer Registry Reporting Content IG. This role is responsible for allowing creation, modification and deletion of Subscriptions and allows searching and retrieval of resources using US Core APIs.

Raw OpenAPI-Swagger Definition file | Download

EHR

(Requirements Definition Capability Statement)

Canonical URL: http://hl7.org/fhir/us/central-cancer-registry-reporting/CapabilityStatement/central-cancer-registry-reporting-ehr

Published by: HL7 International - Public Health Work Group

This profile defines the expected capabilities of the EHR actor to support the central cancer registry reporting use cases. This actor is responsible for publishing Subscription Topics based on Named Events, generate notifications base on subscriptions and support US Core FHIR APIs.

General

FHIR Version: 4.0.1
Supported formats: json

REST behavior

The primary focus of the EHR is to allow the creation, modification and deletion of Subscriptions, notify subscribers based on subscriptions and support US Core APIs.

Security:

Implementations must meet the general security requirements documented in FHIR Security guidance.

In addition the EHR needs to meet the security requirements as outlined in the Formal Specification - Security Section.

US Core Support

The EHR SHALL implement the US Core Server capability statement as foundational FHIR APIs needed by the Central Cancer Registry Reporting IG.


mCode Support

The EHR SHALL implement the mCode profiles outlined to support the Central Cancer Registry Reporting IG.


Resource summary

Resource Search Read Read Version Instance History Resource History Create Update Delete Operations
Backported Subscription SHALL MAY MAY MAY $status
Encounter End Subscription Topic SHALL MAY MAY MAY
Backport Subscription Notification Bundle SHALL
Backport Subscription Status SHALL
US Core APIs SHALL SHALL


Subscription (Includes Subscriptions for encounter-close Subscription Topic)

Profile

Interactions

Name Description
  read

Allows retrieval of a specific Subscription instance.
  create

Allows creation of Subscription instances
  update

Allows Update of Subscription instances
  update

Allows deletion of Subscription instances


Bundle (Notifcation Bundle for Subscriptions)

Profile

Interactions

Name Description
  create

Allows creation of Notifcation Bundles for Subscriptions



Parameters (Parameters Profile to retrieve Subscription Status)

Profile

Interactions

Name Description
  read

Allows clients to request Subscription Status for Subscriptions



US Core APIs

Profile: None

Interactions

Name Description
  search

Allows searching of specific US Core resource profile instances.
  read

Allows retrieval of specific US Core resource profile instances