Difference between revisions of "Registry Content Submission-CathPCI"
JohnMoehrke (talk | contribs) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
==Benefits== | ==Benefits== | ||
| − | The Registry Content Submission-CathPCI v4.4 (RCS-C) Profile has been developed as an IHE Technical Framework implementation to provide an industry standard specification for reporting to the NCDR CathPCI Registry v4.4. Use of an industry standard will reduce the reporting burden on submitters by using the same standard mandated for hospital reporting | + | The Registry Content Submission-CathPCI v4.4 (RCS-C) Profile has been developed as an IHE Technical Framework implementation to provide an industry standard specification for reporting to the NCDR CathPCI Registry v4.4. Use of an industry standard will reduce the reporting burden on submitters by using the same standard mandated for hospital reporting for Meaningful Use, Stage 2. The NCDR Registries help hospitals and private practices measure and improve the quality of cardiovascular care they provide. |
==Details== | ==Details== | ||
| − | The RCS-C | + | The RCS-C profile specifies the content structure and value sets for reporting the data elements collected during a cardiac catheterization and/or PCI to the NCDR. The NCDR CathPCI Registry V4.4Coder’s Data Dictionary stipulates the RCS-C profile data and value sets. |
| − | + | ||
| − | + | The RSC-C profile supports a single use case, Compile and Transfer RSC-Content (i.e., Submission to a CathPCI Registry). In this use case, the Content Creator gathers the data that is required to create the RSC-C document instance. The role of content creator may be filled by a healthcare facility system that documents the cardiac catheterization and PCI procedures. | |
| − | The RSC-C | ||
The Content Creator sends the completed document instance to a Content Consumer. The Content Consumer parses the content and extracts the discrete data. | The Content Creator sends the completed document instance to a Content Consumer. The Content Consumer parses the content and extracts the discrete data. | ||
| Line 24: | Line 23: | ||
'''Template Containment:''' | '''Template Containment:''' | ||
[[File:Template Containment.jpg]] | [[File:Template Containment.jpg]] | ||
| + | |||
| + | ==Systems Affected== | ||
==Specification== | ==Specification== | ||
| Line 32: | Line 33: | ||
'''Documents:''' | '''Documents:''' | ||
| − | + | [http://www.ihe.net/Technical_Frameworks/#cardiology Cardiology Technical Framework:] | |
| − | + | :* [http://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_RCS-C.pdf Registry Content Submission - CathPCI V4.4] - (RCS-C) | |
| − | [http://www.ihe.net/ | + | :* [http://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_RCS-C_Rev1.1_TI_2014-07-18_SampleXMLDocument.xml Sample RCS-C CDA Document] (XML) |
| − | :* [http://www.ihe.net/ | + | :* [http://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_RCS-C_Rev1.1_TI_2014-07-18_SampleDataCollectionForm.pdf Sample RCS-C Data Collection Form] (PDF) |
| − | :* [http://www.ihe.net/ | ||
| − | :* [http://www.ihe.net/ | ||
'''Underlying Standards:''' | '''Underlying Standards:''' | ||
| − | |||
| − | |||
:* [http://www.hl7.org HL7] | :* [http://www.hl7.org HL7] | ||
| − | :* ... | + | :* [http://www.ihtsdo.org SNOMED] |
| + | :* [http://www.loinc.org LOINC] | ||
| + | :* [http://www.nlm.nih.gov/research/umls/rxnorm/ RxNorm] | ||
==See Also== | ==See Also== | ||
| Line 59: | Line 58: | ||
'''Implementer Information''' | '''Implementer Information''' | ||
| − | |||
'''Reference Articles''' | '''Reference Articles''' | ||
| − | + | [[Category:Profiles]] | |
| − | + | [[Category:Cardiac Profile]] | |
| − | + | [[Category:DocShare]] | |
| − | + | [[Category:CDA]] | |
| − | |||
| − | |||
| − | |||
| − | [[Category: | ||
| − | |||
| − | |||
Latest revision as of 14:33, 4 November 2019
This content profile provides an HL7 CDA Implementation Guide for the content needed to support submissions to the NCDR® CathPCI Registry® v4.4.
Summary
The RCS-C Profile specifies the content structure and value sets for reporting the data elements collected during a cardiac catheterization and/or PCI to the NCDR. The NCDR CathPCI Registry V4.4Coder’s Data Dictionary stipulates the RCS-C profile data and value sets.
Benefits
The Registry Content Submission-CathPCI v4.4 (RCS-C) Profile has been developed as an IHE Technical Framework implementation to provide an industry standard specification for reporting to the NCDR CathPCI Registry v4.4. Use of an industry standard will reduce the reporting burden on submitters by using the same standard mandated for hospital reporting for Meaningful Use, Stage 2. The NCDR Registries help hospitals and private practices measure and improve the quality of cardiovascular care they provide.
Details
The RCS-C profile specifies the content structure and value sets for reporting the data elements collected during a cardiac catheterization and/or PCI to the NCDR. The NCDR CathPCI Registry V4.4Coder’s Data Dictionary stipulates the RCS-C profile data and value sets.
The RSC-C profile supports a single use case, Compile and Transfer RSC-Content (i.e., Submission to a CathPCI Registry). In this use case, the Content Creator gathers the data that is required to create the RSC-C document instance. The role of content creator may be filled by a healthcare facility system that documents the cardiac catheterization and PCI procedures. The Content Creator sends the completed document instance to a Content Consumer. The Content Consumer parses the content and extracts the discrete data.
Actors & Transactions:
RCS-C Profile specifies the content structure and value sets for reporting the data elements collected during a cardiac catheterization and/or PCI to the NCDR®
Template Containment:
Systems Affected
Specification
Profile Status: Trial Implementation
Documents:
Cardiology Technical Framework:
Underlying Standards:
See Also
Related Profiles
- Cath Report Content [CRC] format for a CDA report of a cardiac Cath/PCI procedure, including discrete data elements.
Consumer Information
The NCDR CathPCI Coder's Data Dictionary defines the elements that are captured for the NCDR CathPCI v4.4 Registry.
Implementer Information
Reference Articles