When the Registry periodic submission upload would exceed timeout limits or is requested as an NDJSON file, use of this Upload operation is suggested. See the FHIR Asynchronous API for more details on asynchronous FHIR exchange.

A Capability Statement with slicing defined

The Profile for validation responses for CREDS submitted bundles.
Each Operation Outcome begins with the Submission identifier as the first issue entry. Each following issue element contains a single validation message

StructureDefinition for use with CREDS mapping creating the base mappings for FHIR, CDA and V2

This is the standard Bundle to be used with a CREDS submission

All SNOMED codes that are an abnormal Electrocardiac Assessment result

Listing of all antiarrythmics used in CathPCI procedures

Arterial Access Site

All SNOMED Codes that are CABG Procedures

ACC coronary artery bypass graft (CABG) Indications

Coronary Artery Bypass Status

Major Types of CABG

All SNOMED Codes related to Cardiac Arrest

CTA Heart and Coronary arteries

Cardiac CTA Results

SNOMED Cardiac Catheters set

Cardiac Instability Type

Was Patient Referred for Cardiac Rehab

aortic valve, mitral valve, pulmonary valve and tricuspid valve

Decision options for Cardiovascular Treatment consult

All SNOMED Codes that are Cerebrovascular Disease

Chest Pain Symptom Assessment Options

Chronic Lung Disease as defined by ACC

Concomitant Procedures Performed Type

All SNOMED Codes that are Diabetes Mellitus

All SNOMED Codes that are Dyslipidemia

Electrocardiac Abnormality Type

Electrocardiac Assessment Method

Electrocardiac Assessment Results

All codes in SNOMED and LOINC indicating a family history of Premature Coronary Artery Disease Where premature means under 55 if male and under 65 if female

First Cardiac Arrest Rhythm

Functional Capacity in METS

Vessels used for the coronary artery bypass graft

ValueSet listing payment source codes used by ACC

All SNOMED Codes that are Heart Failure

All SNOMED Codes regarding hemodialysis or peritoneal dialysis

All SNOMED Codes that are Hypertension

All SNOMED codes about Induced Hypothermia

Intervention Types Listed at Discharge

Cath PCI qualified list of Events

ACC categories for complexity

Lesion Segment Number

Location in the CABG Graft

Mechanical Ventricular Support Timing

Type of Multi-vessel Procedure Performed

Full SNOMED set for MI

Validation errors from CathPCI submissions

Full NCDR Question Set

NYHA Loinc AnsWerlist

Includes codes from SNOMED and LOINC

Non-Sustained Ventricular Tachycardia Type

All SNOMED codes that are an Organ Donor (person)

Reasons the percutaneous coronary intervention PCI may be performed

POssible codes for PCI Operator

The status of the PCI

SNOMED codes for PRBC

Patient Centered Reason for Delay in PCI Reason

All SNOMED Codes that are PCI Procedures

All SNOMED Codes that are Chronic Lung Disease

All SNOMED and LOINC codes for CABG or Prior CABG

Prior Diagnostic Coronary Angiography Procedure Results

SNOMED CT codes for MI

LOINC codes for Rose Dyspnea Questions

ECG where STEMI or STEMI Equivalent First Noted

LOINC codes for the answers to SA Questions

All LIONC codes for Seattle Angina Questions

• ^experimental = true Patient’s smoking status.
  Includes all SNOMED codes related to smoking status under ‘Finding of tobacco use and exposure (finding)’

Major Types of Stents used in CathPCI procedures

All ACC Selected Stress Tests for the CathPCI submission

Stress Test Results

Stress Test Risk/Extent of Ischemia

Submission Type

Surgeon Identified Risk

Syntax Score options for the PCI procedure

TIMI (Thrombolysis in Myocardial Infarction) flow grades

Valvular Disease Regurgitation Severity

Valvular Disease Stenosis Severity

Existance of Valvular Regurgitation

Loinc codes for Valvular Stenosis

Forms Of Mechanical Support

Specific Options for Ventricular Support Devices

Affirmative or Negative

Sources for Payment for Element 3010

This is the complete list of all codes from the NCDR code list used in selections for the CathPCI questionnaire.

Codes used for CathPCI Question Codes

All errors for CathPCI Validation

This is an example of the data that would be used for a Cath-PCI Submission. The full map is a logical model as that allows conformance to the FHIR Standard the way a custom Resource would not. Each element has the short name of the data, a full description and the paths to fetch and place the information, by data standard type, for each. A section (such as Demographics) is a BackboneElement (holds no values). All subordinate elements are strings. Each mapping includes the following:

• identity = standard used for the mapping (e.g., FHIR)
• language = mime type that matches identity
• map = FHIRPath expression of the path to the data
• comment = Output mapping only Profile for inclusion in the Submission Bundle if not the Core resource

Environment Variables used: %patient (Patient resource for the subject of the procedure) %period (Encounter period i.e. Encounter.period) %procedure (Cath PCI Procedure resource) %procedure.period (CathPCI Procedure period i.e., Procedure.performedPeriod)

This is an example of the data that would be used for a Resgistry Submission. The full map is a logical model as that allows conformance to the FHIR Standard the way a custom Resource would not. Each element has the short name of the data, a full description and the paths to fetch and place the information, by data standard type, for each. A section (such as Demographics) is a BackboneElement (holds no values). All subordinate elements are strings. Each mapping includes the following:

• identity = standard used for the mapping (e.g., FHIR)
• language = mime type that matches identity
• map = FHIRPath expression of the path to the data
• comment = Output mapping only Resource/Profile for inclusion in the Submission Bundle

This is a patient example for the US Core Patient Profile

Example feedback from a CathPCI Submission

A simple example of the CREDS Submission Bundle

Example Encounter for use within the Example Notification Bundle

An example MessageHeader for use within a CREDS Submission Bundle

Example Location for use within the Example Encounter

Example of a US Core R4 Encounter

Defines the requirements for the Registry Submitter.

Defines the requirements for the Registry Submitter implementing the Search / Retrieve Registry Definition transaction.

Defines the requirements for the Registry Submission Definition Creator.

Defines the requirements for the Registry Submission Definition Creator implementing the Create / Update Registry Definition transaction.

Defines the requirements for the Registry Submission Definition Repository.

Defines the requirements for the Registry Submission Definition Repository implementing the Create / Update Registry Definition transaction.

Defines the requirements for the Registry Submission Definition Repository implementing the Search / Retrieve Registry Definition transaction.

This is a practitioner 1 example for the US Core Practitioner Profile

Example of a US Core R4 Organization