Brief Proposal Template: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older editNewer edit →
Samb (talk | contribs)
48 edits
Kevino (talk | contribs)
editor
4,951 edits
No edit summary
Line 12: Line 12:




==1. Proposed Workitem: ''Radiation Oncology workflow with HIS''==
==1. Proposed Workitem: ''<initial working name for profile/whitepaper/etc>''==


* Proposal Editor: ''Sam Brain''
* Proposal Editor: ''<Name of author/editor/contact for the proposal>''
* Editor: ''Sam Brain''  
* Editor: ''<Name of candidate Lead Editor for the Profile, if known>''  
* Date:    N/A (Wiki keeps history)
* Date:    N/A (Wiki keeps history)
* Version: N/A (Wiki keeps history)
* Version: N/A (Wiki keeps history)
* Domain: ''Radiation Oncology''  
* Domain: ''<Domain name (e.g. Radiology)>''  
 
<nowiki> remove this tag
[[Category:RO]]
[[Category:DomainAbbreviation]]
</nowiki> remove this tag too


==2. The Problem==
==2. The Problem==


''There are three main areas where problems arise because of lack of information exchange between the Radiation Oncology Information System (ROIS) and the Hospital Information System (HIS). These are: (1) Patient Demographics, (2) Billing, and (3) Radiation Oncology scheduling and treatment summary.
''<Summarize the integration problem. What doesn’t work, or what needs to work.>''
 
1. '''Patient Demographics'''.
During the Radiation Oncology clinical process, clinical staff typically enter patient demographic data multiple times. For example: into the ROIS at the patient's initial visit to the Radiation Oncology department; at the imaging modality; at the treatment planning workstation.
 
This information is often read manually from patient demographics displayed by the HIS application, and then typed into the Radiation Oncology application, a time-consuming and error-prone process.
 
In addition, if any of the patient's information changes in the HIS (for instance, medical record number), there is no well-defined mechanism for propagating those changes to the ROIS.
 
2. '''Billing.'''
xxx
 


3. '''Rad Onc schedule, and Treatment summary.'''
xxx
''


==3. Key Use Case==
==3. Key Use Case==
Line 59: Line 44:
==5. Discussion==
==5. Discussion==


''This use case is similar to proposal [http://wiki.ihe.net/index.php?title=IHERO_UseCase_ROSWF Radiation Oncology Schedule Work Flow (ROSWF) (from IHE-JRO)] ''
''<Include additional discussion or consider a few details which might be useful for the detailed proposal>''
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''
:''<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>''
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''
:''<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>''
Line 66: Line 51:


''<This is the brief proposal.  Try to keep it to 1 or at most 2 pages>''
''<This is the brief proposal.  Try to keep it to 1 or at most 2 pages>''
''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]

Revision as of 01:30, 5 March 2009


This is a template page. CLICK HERE if you're not sure how to use it.

DO NOT MODIFY this page unless you are changing the template for all future users.


This template is for one or two page IHE workitem proposals for initial review.


<Delete everything in italics and angle brackets and replace with real text. This means delete the angle bracket character and the two quote marks too.>


1. Proposed Workitem: <initial working name for profile/whitepaper/etc>

  • Proposal Editor: <Name of author/editor/contact for the proposal>
  • Editor: <Name of candidate Lead Editor for the Profile, if known>
  • Date: N/A (Wiki keeps history)
  • Version: N/A (Wiki keeps history)
  • Domain: <Domain name (e.g. Radiology)>

remove this tag [[Category:DomainAbbreviation]] remove this tag too

2. The Problem

<Summarize the integration problem. What doesn’t work, or what needs to work.>


3. Key Use Case

<Describe a short use case scenario from the user perspective. The use case should demonstrate the integration/workflow problem.>

<Feel free to add a second use case scenario demonstrating how it “should” work. Try to indicate the people/systems, the tasks they are doing, the information they need, and hopefully where the information should come from.>


4. Standards & Systems

<List existing systems that are/could be involved in the problem/solution.>

<If known, list standards which might be relevant to the solution>


5. Discussion

<Include additional discussion or consider a few details which might be useful for the detailed proposal>

<Why IHE would be a good venue to solve the problem and what you think IHE should do to solve it.>
<What might the IHE technical approach be? Existing Actors? New Transactions? Additional Profiles?>
<What are some of the risks or open issues to be addressed?>


<This is the brief proposal. Try to keep it to 1 or at most 2 pages>


<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>

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