Protocols for Clinical Registry Extraction and Data Submission (CREDS) IG, published by HL7 International / Clinical Interoperability Council. This is not an authorized publication; it is the continuous build for version 1.0.0. This version is based on the current content of https://github.com/HL7/fhir-registry-protocols-ig/ and changes regularly. See the Directory of published versions
This section defines the actors in this implementation guide.
Figure 1.1-1 below shows the actors directly involved in the CREDS Profile and the relevant transactions between them.
Table 3-1 lists the transactions for each actor directly involved in the CREDS Implementation Guide. To claim compliance with this guide, an actor shall support all required transactions (labeled “R”).
The actors in this profile are described in more detail in the sections below.
The Registry Submission Definition Creator manages the definitional artifacts (logical model and transforms) supporting a clinical registry
See the following CapabilityStatement resources for conformance requirements:
The Registry Submission Definition Repository holds the definitions for the registry submission logical model and the tranformations data conforming to that logical model to the submission format.
See the following CapabilityStatement resources for conformance requirements:
The Registry Submitter is responsible for submitting data to a clinical registry.
See the following CapabilityStatement resources for conformance requirements:
The Registry Submission Data Source makes clinical data available to a registry submitter so that it can be submitted to a registry.
See the following CapabilityStatement resources for conformance requirements:
The Registry Submission Consumer accepts and validates registry submissions on behalf of a clinical registry.
See the following CapabilityStatement resources for conformance requirements: