Docstoc

QME-EH_public-comment-lynn

Document Sample
QME-EH_public-comment-lynn Powered By Docstoc
					                                      Quality, Research and Public Health Technical Framework Supplemen
Use the table below to submit comments on 2011 Quality, Research and Public Health (QRPH) Technical Framework Supplem
17, 2011> will be considered in refining the Trial Implementation versions of these supplements to be published in Septembe

Enter you comments using the table below and send by email to qrphcomments@googlegroups.com.

Notes:
1. The 2011 QRPH Profile Supplements are: (list below)
    a. QRPH Quality Measure Execution (QME-EH)
    b. QRPH Quality Measure Definition (QMD-EH)
    c. QRPH Physician Reporting Public Health-Cancer Registry (PRPH-Ca)
    d. QRPH Early Hearing-loss Care Plan (EHCP)
    e. QRPH Mother and Child Health (MCH)
    f. QRPH Retrieve Process for Execution (RPE)
   g. QRPH Clinical Research Document (CRD)
   These documents are available for download at http://www.ihe.net/Technical_Framework/public_comment.cfm.
2. Designate Volume, Section and Line Number for each comment (or designate as "general").
3. Issue: Be brief, but do include enough information to indicate the issue of concern to you.
4. Designate Priority of each comment as High (H), Medium (M), Low (L)
    L: Typo or other minor correction that an editor can manage. Requires no group discussion.
    M: Medium issue or clarification. Requires discussion, but should not lead to long debate.
    H: Important issue where there is major issue to be resolved. Requires discussion and debate.
5. Proposal: Any new text or explanation you have. Suggestions for rewording or improvement are greatly encouraged. Havin


Submitter   Supplement Name     Vol       Section #         Line #
Name
felhofer    QRPH Quality              1               1.7            145
            Measure Execution
            (QME-EH)
felhofer   QRPH Quality        1 figure X.1-1
           Measure Execution
           (QME-EH)




                                                190
felhofer   QRPH Quality
           Measure Execution
           (QME-EH)
felhofer   QRPH Quality        1 X.1            190
           Measure Execution
           (QME-EH)

felhofer   QRPH Quality        1 X.3.1          225
           Measure Execution
           (QME-EH)
felhofer   QRPH Quality                                      243
           Measure Execution
           (QME-EH)




felhofer   QRPH Quality        1 x.3.1 and         247 and
           Measure Execution     x.3.6             291
           (QME-EH)




felhofer   QRPH Quality                                        2
           Measure Execution
           (QME-EH)
felhofer   QRPH Quality        1 x.3.4                       269
           Measure Execution
           (QME-EH)




felhofer   QRPH Quality        2 5.1 and 6.x
           Measure Execution
           (QME-EH)
felhofer   QRPH Quality        2                   6.3.X
           Measure Execution
           (QME-EH)
felhofer   QRPH Quality        2             360 6.3.2.A
           Measure Execution
           (QME-EH)


felhofer   QRPH Quality        2             405 6.3.2.A
           Measure Execution
           (QME-EH)
felhofer   QRPH Quality        2             415 6.3.2.D
           Measure Execution
           (QME-EH)

felhofer   QRPH Quality
           Measure Execution
           (QME-EH)            2             690 6.3.2.B
felhofer   QRPH Quality
           Measure Execution
           (QME-EH)            2             703             6.5
felhofer   QRPH Quality
           Measure Execution
           (QME-EH)            2   705 6.5.A.1
felhofer   QRPH Quality
           Measure Execution
           (QME-EH)            2   772 6.5.J.2
 search and Public Health Technical Framework Supplement Public Comment Form
1 Quality, Research and Public Health (QRPH) Technical Framework Supplements to the IHE QRPH Technical Committee. Comments subm
mplementation versions of these supplements to be published in September 2011.

end by email to qrphcomments@googlegroups.com.


elow)

 )
ncer Registry (PRPH-Ca)




  http://www.ihe.net/Technical_Framework/public_comment.cfm.
r each comment (or designate as "general").
ion to indicate the issue of concern to you.
 , Medium (M), Low (L)
 r can manage. Requires no group discussion.
ussion, but should not lead to long debate.
 o be resolved. Requires discussion and debate.
e. Suggestions for rewording or improvement are greatly encouraged. Having a new proposal makes it easier for committee members to a


            Issue


            Write these bullets as if the contents of this document were
            being added to the QRPH technical framework. You do not
            need to maintain the history (eg "developed as part of a
            broader integration profile" and "…was extracted from this
            profile and published as public comment..."
I don't think you intend to have a transaction directly
between the Content Creator and Content Consumer in this
profile. Rather, this is a content profile in the context of
RPE, is it not? In that case, remove the QRPH RPE Y4
transaction and group your actors, instead with the
appropriate actors in RPE or the XD* profiles.

The dilemma, of course, is that you specify an optional
grouping of your Content Creator with a
ProcessActivityExecutor and your Content Consumer with a
ProcessStateManager, then the requirements for those actors
in RPE are more than just the Initiate Process transaction. If
you don't want all of that, then you have a challenge. In the
end, you may end up with this one 'Initiate Process'
transaction as an optional transaction betw your Content
Creator & Consumer...then you have the problem of that
transaction talking about the RPE actors in its specification,
and not a content creator/consumer


You are missing an actor/transaction table. Even if you end
up with just 'Share content', you need this section/table.

If this profile is dependent on the QRPH Y4 RPE profile,
these both need to be published for Trial Implementation
together. If RPE is not published, references to it must be
removed.
"The QME-EH MAY be grouped with any of the XD*
transports."

The IHE terminology is a bit 'off' here. You cannot group a
profile with a transport. Instead a profile/actor pair is
grouped with another profile/actor. So you would say
something like: "QME-EH Content Creator may be grouped
with an XDS.b Document Source, an XDR Document
Source, an XDM Portable Media Creator or an RPE
ProcessActivityExecutor."

Note that if your intent is that at least on of these groupings
is mandated, then you have to state that with "shall"
language. You have a statement similar to this in line 245
and 250, but you use "must" and you don't mention RPE.

You would have an analagous statement for the QME-EH
Content Consumer
Be clear about the grouping rqmts and their implications.




I don't understand the table in this section (I haven't seen this
in other profile). If you mean that these actors may be
optionally grouped, you shouldn't use the term "Binding". In
fact, if a QME-EH Content Creator is grouped with a 'source'
actor in XDS, XDM, or XDR, the "Binding" requirements in
PCC TF-2:4.1 are not optional at all.




Fix name of profile




Additions to these sections belong in the CDA Modules Trial
Implementation Supplement.



I am not aware that IHE typically includes "SHALL" in all upper case as you have done here.
This is where the content for this profile is specified. In
Volume 1, you refer to "Quality Measure Execution - Early
Hearing Content". That terminology is not used here. How
is an implementor to make a link between Volume 1 and
Volume 2 for this profile.
You are missing the "Format Code" subsection of the
Document Content Module. It would come before the
LOINC Code section.
The entries in the Template Name column contain links to
the wiki. Is the wiki normative, or is IHE phasing out the
wiki as the source of rqmts for content documention?



wrong profile reference.


fix profile name
what role does this metadata play if QME-EH content is shared in an RPE context?
finish incomplete entries
work Supplement Public Comment Form
Framework Supplements to the IHE QRPH Technical Committee. Comments submitted by <July
blished in September 2011.




mment.cfm.




y encouraged. Having a new proposal makes it easier for committee members to address the


             Proposed Change                                          Priority


                                                                      L
                                                                     M




                                                                     H


                                                                     H



Please clarify and state your grouping rqmts in one paragraph. If you H
mandate grouping at all, you must modify the dependency table in
2.1. Once you determine the profile/actor and grouping structure
you want, write an IHE Integration statement for a product that
would implement this profile. Make sure this makes sense.
Actors from the ITI XDS, XDM and XDR profiles embody the               M
Content Creator and Content Consumer sharing function of this
profile. A Content Creator or Content Consumer shall must be
grouped with appropriate actors from the XDS, XDM or XDR
profiles, and the metadata sent in the document sharing or
interchange messages has specific relationships (which we call
binding) to the content of the clinical document described in the this
content profile. Requirements for Medical Document Binding to
XDS, XDM and XDR are specifiied in PCC TF-2: 4.1.


See previous proposed change.                                            H




A Content Creator Actor and Content Consumer Actor may support
the Enhanced Sharinged Value Set (ESVS) Integration Profile to
receive a common, uniform nomenclature managed. The
Value subsets supporting this profile are described in the appendix of
this document.

also fix section heading

                                                                         M




Although a case can be made that SHALL in upper case makes the requirement more visible, I think this supplement should fo
Use consistent terminology.                                              M




                                                                         L


                                                                         L




replace EHCP with QME-EH                                                 L


IHE ITI TF Enhances Sharing of Value Sets (ESVS) profile.                L
H content is shared in an RPE context?   M


                                         L
k this supplement should follow the IHE convention of using "shall" language for mandatory requirements, but not putting the word in up
ts, but not putting the word in upper case
QRPH Quality Measure Execution (QME-EH)
QRPH Quality Measure Definition (QMD-EH)
QRPH Physician Reporting Public Health-Cancer Registry (PRPH-Ca)
QRPH Early Hearing-loss Care Plan (EHCP)
QRPH Mother and Child Health (MCH)
QRPH Retrieve Process for Execution (RPE)
QRPH Clinical Research Document (CRD)

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:17
posted:8/13/2012
language:
pages:20