Difference between revisions of "PCC Profile Proposal Template"

From IHE Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
[[PCC_Home]]
+
[[PCC| back to PCC homepage]]
 
+
=IHE PCC Profile Proposal=
*Proposed Profile Name: <fill in Name>
+
*Proposed Profile Name: ''<fill in Name>''
*Proposal Date: <date profile is proposed>
+
*Proposal Date: ''<date profile is proposed>''
*Status: Proposed
+
*Status: ''<Proposed|Accepted|Postponed>''
*Version History: <list related profile proposals>
+
*Version History: ''<list related profile proposals>''
 
*Editors:
 
*Editors:
{|-
+
''{|-
 
|Name
 
|Name
 
|Affilliation
 
|Affilliation
Line 15: Line 15:
 
|<your e-mail>
 
|<your e-mail>
 
|-
 
|-
|}
+
|}''
  
 
==1. Brief Description of the Problem:==
 
==1. Brief Description of the Problem:==
<briefly describe the interoperability problem needing to be solved>
+
''<briefly describe the interoperability problem needing to be solved>''
  
 
==2. Key Use Cases==
 
==2. Key Use Cases==
<list the use cases.  This is an example of how the interactions work, both now, and as proposed.>
+
''<list the use cases.  This is an example of how the interactions work, both now, and as proposed.>''
  
 
===Use Case 1: <use case name>===
 
===Use Case 1: <use case name>===
 
===Users:===
 
===Users:===
<list the roles touched in the flow (ie Attending Physician, Consulting Physician)>
+
''<list the roles touched in the flow (ie Attending Physician, Consulting Physician)>''
 
===Systems:===
 
===Systems:===
<list the type of computer systems needing to interoperate (ie HIS, EDIS, RIS, EMR, ...)>
+
''<list the type of computer systems needing to interoperate (ie HIS, EDIS, RIS, EMR, ...)>''
 
===Data:===
 
===Data:===
<list the types of data exchanged (ie Meds, Labs, Orders, Images, Reports, ...)>
+
''<list the types of data exchanged (ie Meds, Labs, Orders, Images, Reports, ...)>''
 
===Current Flow:===
 
===Current Flow:===
<describe the workflow of the current situation and list where potential problems occur.  For example: "First, the Physician (a user) fills out the Prescription (type of data) in his EMR (type of system)".  Next, physician prints out the prescription and gives it to the patient.  Next the patient takes the prescription to the pharmacist which creates a potential for the prescription being lost.  Next, the pharmacist manually enters the script information into his system which creates a possible transcription error. ...>
+
''<describe the workflow of the current situation and list where potential problems occur.  For example: "First, the Physician (a user) fills out the Prescription (type of data) in his EMR (type of system)".  Next, physician prints out the prescription and gives it to the patient.  Next the patient takes the prescription to the pharmacist which creates a potential for the prescription being lost.  Next, the pharmacist manually enters the script information into his system which creates a possible transcription error. ...>''
 
===Proposed Flow if profile implemented:===
 
===Proposed Flow if profile implemented:===
<describe the flow you would like to see happen using the technique.>
+
''<describe the flow you would like to see happen using the technique.>''
  
 
===Use Case 2: <use case name>===
 
===Use Case 2: <use case name>===
<next use case.  you can have as many as needed to fully describe.>
+
''<next use case.  you can have as many as needed to fully describe.>''
  
 
==3. Standards that might Apply==
 
==3. Standards that might Apply==
<list standards that you think might be relevant.  Eg, HL7 CDA, HL7 CCD, SNOMED-CT, ...>
+
''<list standards that you think might be relevant.  Eg, HL7 CDA, HL7 CCD, SNOMED-CT, ...>''
  
 
==4. Further Discussion==
 
==4. Further Discussion==
<further describe evidence of need for the profile. (ie medical evidence that supports need, reference ONC use case, etc)>
+
''<further describe evidence of need for the profile. (ie medical evidence that supports need, reference ONC use case, etc)>''
  
 
==5. Resources/People that could help.==
 
==5. Resources/People that could help.==
<list people that could help the technical committee define, clarify and write the proposal.  Also list skills of that person(ie Technical experience vs clinical experience).  Bringing resources to the table increases the probability that the profile can be done.>
+
''<list people that could help the technical committee define, clarify and write the proposal.  Also list skills of that person(ie Technical experience vs clinical experience).  Bringing resources to the table increases the probability that the profile can be done.>''

Latest revision as of 11:27, 21 July 2008

back to PCC homepage

IHE PCC Profile Proposal

  • Proposed Profile Name: <fill in Name>
  • Proposal Date: <date profile is proposed>
  • Status: <Proposed|Accepted|Postponed>
  • Version History: <list related profile proposals>
  • Editors:

{|- |Name |Affilliation |e-mail |- |<your name> |<your organization> |<your e-mail> |- |}

1. Brief Description of the Problem:

<briefly describe the interoperability problem needing to be solved>

2. Key Use Cases

<list the use cases. This is an example of how the interactions work, both now, and as proposed.>

Use Case 1: <use case name>

Users:

<list the roles touched in the flow (ie Attending Physician, Consulting Physician)>

Systems:

<list the type of computer systems needing to interoperate (ie HIS, EDIS, RIS, EMR, ...)>

Data:

<list the types of data exchanged (ie Meds, Labs, Orders, Images, Reports, ...)>

Current Flow:

<describe the workflow of the current situation and list where potential problems occur. For example: "First, the Physician (a user) fills out the Prescription (type of data) in his EMR (type of system)". Next, physician prints out the prescription and gives it to the patient. Next the patient takes the prescription to the pharmacist which creates a potential for the prescription being lost. Next, the pharmacist manually enters the script information into his system which creates a possible transcription error. ...>

Proposed Flow if profile implemented:

<describe the flow you would like to see happen using the technique.>

Use Case 2: <use case name>

<next use case. you can have as many as needed to fully describe.>

3. Standards that might Apply

<list standards that you think might be relevant. Eg, HL7 CDA, HL7 CCD, SNOMED-CT, ...>

4. Further Discussion

<further describe evidence of need for the profile. (ie medical evidence that supports need, reference ONC use case, etc)>

5. Resources/People that could help.

<list people that could help the technical committee define, clarify and write the proposal. Also list skills of that person(ie Technical experience vs clinical experience). Bringing resources to the table increases the probability that the profile can be done.>