Ihero job jar: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 65: | Line 65: | ||
| align="center" | | | align="center" | | ||
|- | |- | ||
| align="left" | IHE-RO compliance | | align="left" | Physician communication strategy and IHE-RO compliance | ||
| align="left" | Define what IHE-RO compliance means. <br>IHE-RO compliant planner means …<br>IHE-RO compliant advanced planner means … <br> reference IHE-RO helper | | align="left" | Develop simple concise statement of “what does this mean to me in the clinic ?”<br>Define what IHE-RO compliance means. <br>IHE-RO compliant planner means …<br>IHE-RO compliant advanced planner means … <br> reference IHE-RO helper<br> | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | RO | | align="center" | RO | ||
| align="center" | | | align="center" | | ||
| Line 109: | Line 109: | ||
| align="left" | NROR | | align="left" | NROR | ||
| align="left" | Provide interface to National Radiation Oncology Registry | | align="left" | Provide interface to National Radiation Oncology Registry | ||
| align="left" | | | align="left" | 1 | ||
| align="center" | | | align="center" | MP | ||
| align="center" | | | align="center" | | ||
|- | |- | ||
| Line 124: | Line 124: | ||
| align="left" | SAM | | align="left" | SAM | ||
| align="left" | Prepare content for SAM | | align="left" | Prepare content for SAM | ||
| align="left" | | | align="left" | 2 | ||
| align="center" | RO | | align="center" | RO | ||
| align="center" | Kevin, Tony, Ramesh, Akkamma, Colin, Rishabh | | align="center" | Kevin, Tony, Ramesh, Akkamma, Colin, Rishabh | ||
| Line 130: | Line 130: | ||
| align="left" | Distribution of info | | align="left" | Distribution of info | ||
| align="left" | Take IHE-RO message to other meetings (Lung, GU, etc). Stop giving talks to ourselves | | align="left" | Take IHE-RO message to other meetings (Lung, GU, etc). Stop giving talks to ourselves | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | RO | | align="center" | RO, Publications | ||
| align="center" | | | align="center" | | ||
|- | |- | ||
| align="left" | Use Case Selection | | align="left" | Use Case Selection | ||
| align="left" | Organize use case solicitation, definition, selection, prioritization, interface with TC | | align="left" | Organize use case solicitation, definition, selection, prioritization, interface with TC | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | MP, V | | align="center" | MP, V | ||
| align="center" | Colin, Adam, David, Sidrah, all PC during process | | align="center" | Colin, Adam, David, Sidrah, all PC during process | ||
|- | |- | ||
| align="left" | Use Case | | align="left" | Use Case Follow-up | ||
| align="left" | Followup with individuals who submitted as use case to let them know what is happening | | align="left" | Followup with individuals who submitted as use case to let them know what is happening | ||
| align="left" | | | align="left" | 2 | ||
| align="center" | MP, V | | align="center" | MP, V | ||
| align="center" | | | align="center" | | ||
| Line 154: | Line 148: | ||
| align="left" | IHE-RO helper | | align="left" | IHE-RO helper | ||
| align="left" | Web-based tool to publicize document IHE-RO solutions | | align="left" | Web-based tool to publicize document IHE-RO solutions | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | MP | | align="center" | MP | ||
| align="center" | Rishabh (short term), ?? (long term) | | align="center" | Rishabh (short term), ?? (long term) | ||
| Line 160: | Line 154: | ||
| align="left" | Connectathon Judging | | align="left" | Connectathon Judging | ||
| align="left" | Attend the connectathon and serve as an independent judge | | align="left" | Attend the connectathon and serve as an independent judge | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | MP | | align="center" | MP | ||
| align="center" | Lakshmi | | align="center" | Lakshmi | ||
| Line 166: | Line 160: | ||
| align="left" | Wiki | | align="left" | Wiki | ||
| align="left" | keep it up to date | | align="left" | keep it up to date | ||
| align="left" | | | align="left" | 2.5 | ||
| align="center" | MP | | align="center" | MP | ||
| align="center" | Colin, Sidrah | | align="center" | Colin, Sidrah | ||
| Line 172: | Line 166: | ||
| align="left" | RT Process flowchart | | align="left" | RT Process flowchart | ||
| align="left" | Look at process map and re-examine where we have use cases on it (safety, workflow) | | align="left" | Look at process map and re-examine where we have use cases on it (safety, workflow) | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | MP | | align="center" | V, MP | ||
| align="center" | | | align="center" | | ||
|- | |- | ||
| align="left" | Patient Archive | | align="left" | Patient Archive | ||
| align="left" | Develop Use Case, vision to include long term goal of providing a patient archive with patient access. EMR requirements ? | | align="left" | Develop Use Case, vision to include long term goal of providing a patient archive with patient access. EMR requirements ? Could be tied to RT Process flowchart. Should be this be dealt with as a use case ? | ||
| align="left" | | | align="left" | 1 | ||
| align="center" | MP | | align="center" | MP | ||
| align="center" | | | align="center" | | ||
| Line 184: | Line 178: | ||
| align="left" | Communications | | align="left" | Communications | ||
| align="left" | Interactions with technical groups (e.g. TC, RT Shareholders, NEMA, others) | | align="left" | Interactions with technical groups (e.g. TC, RT Shareholders, NEMA, others) | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | MP | | align="center" | MP | ||
| align="center" | | | align="center" | | ||
| Line 190: | Line 184: | ||
| align="left" | Business Model | | align="left" | Business Model | ||
| align="left" | Manage our budget, set fee structures, develop funding opportunities. How do we use resources. | | align="left" | Manage our budget, set fee structures, develop funding opportunities. How do we use resources. | ||
| align="left" | | | align="left" | 4 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
| Line 196: | Line 190: | ||
| align="left" | Connectathons | | align="left" | Connectathons | ||
| align="left" | Support TC for connectathon planning and execution | | align="left" | Support TC for connectathon planning and execution | ||
| align="left" | | | align="left" | 2 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
| Line 202: | Line 196: | ||
| align="left" | ESTRO Connectathon ? | | align="left" | ESTRO Connectathon ? | ||
| align="left" | Will we have a presence at ESTRO ? | | align="left" | Will we have a presence at ESTRO ? | ||
| align="left" | | | align="left" | 4 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
| Line 208: | Line 202: | ||
| align="left" | Fund raising | | align="left" | Fund raising | ||
| align="left" | Identify and approach (or organize request) to organizations for funding | | align="left" | Identify and approach (or organize request) to organizations for funding | ||
| align="left" | | | align="left" | 2 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
| Line 214: | Line 208: | ||
| align="left" | Closing the Loop | | align="left" | Closing the Loop | ||
| align="left" | Ensure vendors release products into the RO market within a certain time period from when the products passed at a Connectathon | | align="left" | Ensure vendors release products into the RO market within a certain time period from when the products passed at a Connectathon | ||
| align="left" | | | align="left" | 3 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
| Line 220: | Line 214: | ||
| align="left" | Re-testing at connectathons | | align="left" | Re-testing at connectathons | ||
| align="left" | Prepare guidance document for re-testing at connectathon | | align="left" | Prepare guidance document for re-testing at connectathon | ||
| align="left" | | | align="left" | 4 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
| Line 226: | Line 220: | ||
| align="left" | Test Laboratory | | align="left" | Test Laboratory | ||
| align="left" | Figure out what IHE-RO needs to do | | align="left" | Figure out what IHE-RO needs to do | ||
| align="left" | | | align="left" | 4 | ||
| align="center" | V | | align="center" | V | ||
| align="center" | | | align="center" | | ||
Revision as of 10:04, 16 March 2012
The IHE-RO Job Jar
The creation of a 'job jar' to collect tasks, prioritize them, and solicit volunteers.
The Priority correspond to the following
- 3 - High Priority
- 2 - Medium Priority
- 1 - Low Priority
- 0 - Should be removed from the list
The PC Co-Chair corresponds to one or more of the following:
- RO - Radiation Oncologist
- MP - Medical Physicist
- V - Vendor
- Publications - Publications Committee
Volunteers that have been identified should not be considered as owning the task. Other assistance is appreciated; please contact one of the following.
RO: Ramesh Rengan, rengan<at>xrt.upenn.edu ?
MP: Colin Field, colin.field<at>albertahealthservices.ca
V: Adam Earwicker, adam.earwicker<at>varian.com
Secretariat: Sidrah Abdul, sidraha<at>astro.org
Please replace <at> with @ to generate the correct email address.
IHE-RO Job Jar
| Job | Description | Priority (3,2,1,0) | PC Co-Chair Responsible | Volunteers |
|---|---|---|---|---|
| PC TCONs & meetings | Organize Calls | 4 | RO, MP, V | Sidrah |
| IHE Vision Document | Prepare and Update annually | 4 | RO, MP, V | Colin, Sidrah |
| IHE-RO Structure | Establish and publicize Terms of Reference, Position Terms, Succession planning | 4 | RO, MP, V | |
| Job Jar | Organize and maintain the job jar | 4 | RO, MP, V | |
| PC and TC Membership and participation | Recruit volunteers for IHE-RO effort. Identify new stakeholders, and volunteers from other countries | 3 | RO, MP, V, TC co-chairs | |
| Physician communication strategy and IHE-RO compliance | Develop simple concise statement of “what does this mean to me in the clinic ?” Define what IHE-RO compliance means. IHE-RO compliant planner means … IHE-RO compliant advanced planner means … reference IHE-RO helper |
3 | RO | |
| IHE Communications | Participate in IHE co-chair TCONs | 4 | RO, MP, V | Sidrah, Bruce, rotate through PC co-chairs |
| Other IHE-RO country domains | Communicate with other IHE-RO country domains, e.g. Japan, Netherlands | 3 | V | |
| FDA | Prepare white paper (details needed) USA specific. | 2 | RO | |
| Publications and promotion | Organize all communications with RO community | 3 | MP | Charles, Akkamma |
| IHE Webinar | Prepare and give IHE Webinars | 1 | Publications | Colin, Bruce |
| Connectathon results | Publicize results (via IHE-RO helper) | 3 | RO, MP | Bruce |
| NROR | Provide interface to National Radiation Oncology Registry | 1 | MP | |
Each profile in development
|
provide continual feedback to the TC for development of the profiles and reports progress back to the PC. Provide evaluation of completed profiles (make it user case specific) | 3 | V | |
| SAM | Prepare content for SAM | 2 | RO | Kevin, Tony, Ramesh, Akkamma, Colin, Rishabh |
| Distribution of info | Take IHE-RO message to other meetings (Lung, GU, etc). Stop giving talks to ourselves | 3 | RO, Publications | |
| Use Case Selection | Organize use case solicitation, definition, selection, prioritization, interface with TC | 3 | MP, V | Colin, Adam, David, Sidrah, all PC during process |
| Use Case Follow-up | Followup with individuals who submitted as use case to let them know what is happening | 2 | MP, V | |
| IHE-RO helper | Web-based tool to publicize document IHE-RO solutions | 3 | MP | Rishabh (short term), ?? (long term) |
| Connectathon Judging | Attend the connectathon and serve as an independent judge | 3 | MP | Lakshmi |
| Wiki | keep it up to date | 2.5 | MP | Colin, Sidrah |
| RT Process flowchart | Look at process map and re-examine where we have use cases on it (safety, workflow) | 3 | V, MP | |
| Patient Archive | Develop Use Case, vision to include long term goal of providing a patient archive with patient access. EMR requirements ? Could be tied to RT Process flowchart. Should be this be dealt with as a use case ? | 1 | MP | |
| Communications | Interactions with technical groups (e.g. TC, RT Shareholders, NEMA, others) | 3 | MP | |
| Business Model | Manage our budget, set fee structures, develop funding opportunities. How do we use resources. | 4 | V | |
| Connectathons | Support TC for connectathon planning and execution | 2 | V | |
| ESTRO Connectathon ? | Will we have a presence at ESTRO ? | 4 | V | |
| Fund raising | Identify and approach (or organize request) to organizations for funding | 2 | V | |
| Closing the Loop | Ensure vendors release products into the RO market within a certain time period from when the products passed at a Connectathon | 3 | V | |
| Re-testing at connectathons | Prepare guidance document for re-testing at connectathon | 4 | V | |
| Test Laboratory | Figure out what IHE-RO needs to do | 4 | V | |