Difference between revisions of "Brief Proposal Template"

Latest revision as of 13:20, 13 October 2010

This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and copy the contents of this page and paste the contents into your newly created page.

<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.>

<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>

3. Key Use Case

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

4. Standards and 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.>

@@ Line 1: / Line 1: @@
 __NOTOC__
-=IHE Profile Proposal (Brief)=
+''This template is for one or two page IHE workitem proposals for initial review. To create a new proposal, first log in to the Wiki (or create an account if you don't already have one). Then create an appropriately named new Wiki page (see the editing instructions linked to "Help" at left. Then come back to this page, click "edit" above, select and '''copy''' the contents of this page and paste the contents into your newly created page.''
-==1. Proposed Profile: ''<initial working name for profile>''==
+''<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.>''
-* Proposal Editor: ''Christophe Trébuchet(CH Sud Réunion)  (Karima Bourquard (GMSIH)
+==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: ''<…ITI/GMSIH and CH Sud Réunion>''
+* Domain: ''<Domain name (e.g. Radiology)>''
+<nowiki> remove this tag
+[[Category:DomainAbbreviation]]
+</nowiki> remove this tag too
 ==2. The Problem==
-In hospitals, the centralized appointment solutions are more and more frequently implemented and used. They are interfaced with care management solutions, EMR or with the patient agendas and resources.
+''<Summarize the integration problem. What doesn’t work, or what needs to work.>''
-Because of the lack of a good integration between centralized appointment solutions and RIS or any others healthcare solutions, several problems will be occured:
--	collusion between radiology appointment with others appointments ;
--	no possibility to take appointments  in radiology following or preceding others appointments in other specialties ;
--	no possibility to take a radiology appointment with the attendance of a non radiologist resource ;
--	no possibility to consult radiology appointments inside the  care management.
+''<Now describe the Value Statement: what is the underlying cost incurred by the problem, what is to be gained by solving it>''
 ==3. Key Use Case==
-An easy answer to solve this problem is possible today because of the improvement of the management of the resources inside of the most common centralized appointment management solutions.
+''<Describe a short use case scenario from the user perspective.  The use case should demonstrate the integration/workflow problem.>''
-The management of the radiology resources , appointments and agendas will be done in the centralized solution. Then it is necessary to create a workflow between the RIS and the centralized appointment solution for each appointment with the given data : date, hour, room, act, radiologist, devices.
-The RIS will register as usual the patient when patient arrives in radiology department and the rest of the procedures is the same.
-The workflow between RIS and the EMR will be the same that already described in the radiology workflow (feedback from radiology department :  radiology report, state of the appointment,…).
-This answer can give the possibility to hospitals to use a unique centralized appointment solution. It can be also used by any solution in a ward department using a specific appointment management solution.
+''<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==
+==4. Standards and Systems==
-   The general workflow will be the following :
-Schema : see document
+''<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?>''
-Actors :
+''<This is the brief proposal.  Try to keep it to 1 or at most 2 pages>''
-Appointment Requester (AR): this system requests for placing a new appointment for a patient according to the others constraints
-Appointment Filler (AF): this system, after managing the requests and validation by the appointment requester, sends to the appointment tracker all the datas of the new appointment for the patient
-Appointment Tracker (AT): after receiving the appointment, permits to the user to consult a particular or a list of appointment for one or several patients. It also publishes the status of the appointment given by the Order Placer (in the ward) or the Order Filler in the others departments.
-The standards which could  be used are HL7V2.5 or V3
-==5. Discussion==
-this kind of profile is under the competency of IHE. This problem was discussed between memebers of IHE few years ago with no answer. Because of the maturity of the domain and memebers in IHE, I am confident that it is now possible to solve it in ITI domain. The reason is that the appointment is a transversal function in the Hospital IT.
+''<Delete this Category Templates line since your specific Profile Proposal page is no longer a template.>'' [[Category:Templates]]