CRD Notes 2011: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older edit
 
(21 intermediate revisions by the same user not shown)
Line 2: Line 2:




==Heading 1==
=CRD Clarifications for Implementers=


'''Bold text is encoded in double quotes''' - regular text goes here
In developing this year’s trial supplements, the QRPH Technical Committee has made significant progress toward creating a unified Quality, Research and Public Health technical framework.  Since the CRD profile was not revised during this current cycle, the specifications in that supplement have not yet benefited from the recent developments.  The information below provides clarifications which are intended to refine the CRD specifications to align the profile with the emerging QRPH technical framework and address any present gaps in the existing CRD documentation.
Note that the table of contents is built automatically, contents of the TOC come from the items in your heading lines
<br>
<br>
[[image:CRD_Clarification.jpg|thumbnail|center|600px|'''Clarified CRD Actor Transaction Diagram with Annotation Augmentation''']]
<br>
===Figure: CRD Clarification for Implementers===
The figure above shows the key points of clarification required to bridge the gap between the current CRD Technical Supplement and the 2012 Gazelle testing implementation. The clarifications included here are not normative. However, they are informative, and are considered by the QRPH committee to improve the consistency and accuracy of the information provided in the current CRD profile documentation. Where differences occur between this information and the profile documentation, implementers need to be aware that these clarifications supercede so far as 2012 Connectathon testing is concerned.
<br>


==Benefits==
==Content Document Creation==


'''More bold text'''
Form Fillers in the CRD profile will undergo a Content Creator test to validate the creation of a CRD Content Document. A CRD Content Document is a CCD document with further constraints defined within the CRD profile.
Another paragraph    we will replace the figure below with your jpg
<br><br>
The CRD content document template uses the CCD template as a parent and then further constrains some of the header elements and the inclusion conformance for the sections. 
<br>
The CRD template id establishing these additional constraints is 1.3.6.1.4.1.19376.1.7.3.1.1.10
<br>
<br>
The LOINC code establishing the type of document is a direct inheritance from the CCD parent template.
<br>
The CRD LOINC code is 34133-9, "Summary of Episode Note"
<br>


==Actor Options==
A system signing up for the Archive_CRD option for the Form Filler actor will be required to initiate an ITI-41 transaction, playing the role of the Document Source actor in the ITI-41 specification.
<br>




'''Actors & Transactions:'''
==Actor Groupings==
Systems signing up to play the role of the Form Archiver in the CRD profile also will be required to sign up for the Form Archiver actor in the RFD profile.  Validation of the ITI-36 transaction to archive the form instance will be performed during testing of the RFD profile.
<br>


[[image:XUA_Actors_Figure_05.jpg|thumbnail|center|600px|'''This is the name of your figure.  We will upload a jpg and point to it in this line''']]


==Specification==
==Transactions==
 
When reading the ITI-41 Provide and Register documentation, in the context of implementing the CRD profiIe, the CRD Form Filler will play the role of the Document Source actor and the CRD Form Archiver will play the role of the Document Recipient. For detailed documentation on the ITI-41 transaction, refer to the ITI Vol 2b. [http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Rev8-0_Vol2b_FT_2011-08-19.pdf ITI Technical Framework Volume 2b]
In the next line, you will see how to encode a link. The first part is the web address, then a space, then a phrase that appears as the link on the page
 
'''Documents:'''
[http://www.ihe.net/Technical_Framework/index.cfm#IT IHE IT Infrastructure Technical Framework Version 5 or later]
:* Vol. 1 - Section 13
:* Vol. 2(b) - Sections 3.40
 
==Another Header==
* sample bullet list.  1st level is preceded by a star
** sub bullet items preceded by 2 stars
** another sub bullet
** another sub bullet

Latest revision as of 11:02, 15 September 2011


CRD Clarifications for Implementers

In developing this year’s trial supplements, the QRPH Technical Committee has made significant progress toward creating a unified Quality, Research and Public Health technical framework. Since the CRD profile was not revised during this current cycle, the specifications in that supplement have not yet benefited from the recent developments. The information below provides clarifications which are intended to refine the CRD specifications to align the profile with the emerging QRPH technical framework and address any present gaps in the existing CRD documentation.

Clarified CRD Actor Transaction Diagram with Annotation Augmentation


Figure: CRD Clarification for Implementers

The figure above shows the key points of clarification required to bridge the gap between the current CRD Technical Supplement and the 2012 Gazelle testing implementation. The clarifications included here are not normative. However, they are informative, and are considered by the QRPH committee to improve the consistency and accuracy of the information provided in the current CRD profile documentation. Where differences occur between this information and the profile documentation, implementers need to be aware that these clarifications supercede so far as 2012 Connectathon testing is concerned.

Content Document Creation

Form Fillers in the CRD profile will undergo a Content Creator test to validate the creation of a CRD Content Document. A CRD Content Document is a CCD document with further constraints defined within the CRD profile.

The CRD content document template uses the CCD template as a parent and then further constrains some of the header elements and the inclusion conformance for the sections.
The CRD template id establishing these additional constraints is 1.3.6.1.4.1.19376.1.7.3.1.1.10

The LOINC code establishing the type of document is a direct inheritance from the CCD parent template.
The CRD LOINC code is 34133-9, "Summary of Episode Note"

Actor Options

A system signing up for the Archive_CRD option for the Form Filler actor will be required to initiate an ITI-41 transaction, playing the role of the Document Source actor in the ITI-41 specification.


Actor Groupings

Systems signing up to play the role of the Form Archiver in the CRD profile also will be required to sign up for the Form Archiver actor in the RFD profile. Validation of the ITI-36 transaction to archive the form instance will be performed during testing of the RFD profile.


Transactions

When reading the ITI-41 Provide and Register documentation, in the context of implementing the CRD profiIe, the CRD Form Filler will play the role of the Document Source actor and the CRD Form Archiver will play the role of the Document Recipient. For detailed documentation on the ITI-41 transaction, refer to the ITI Vol 2b. ITI Technical Framework Volume 2b

Retrieved from "http://wiki.ihe.net/index.php?title=CRD_Notes_2011&oldid=54093"