Ihero job jar: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Cfield (talk | contribs)
Cfield (talk | contribs)
Line 29: Line 29:
=== IHE-RO Job Jar  ===
=== IHE-RO Job Jar  ===


{| cellspacing="1" cellpadding="1" border="1" width="800" class="wikitable sortable"
{| width="800" cellspacing="1" cellpadding="1" border="1" class="wikitable sortable"
|-
|-
! align="center" width="75" | Job
! align="center" width="75" | Job  
! align="center" width="250" | Description  
! align="center" width="250" | Description  
! align="center" width="75" | Priority (3,2,1,0)  
! align="center" width="75" | Priority (3,2,1,0)  
Line 39: Line 39:
| align="left" | PC TCONs & meetings  
| align="left" | PC TCONs & meetings  
| align="left" | Organize Calls  
| align="left" | Organize Calls  
| align="left" | 5
| align="center" | 5  
| align="center" | RO, MP, V  
| align="center" | RO, MP, V  
| align="center" | Sidrah
| align="center" | Sidrah
Line 45: Line 45:
| align="left" | IHE Vision Document  
| align="left" | IHE Vision Document  
| align="left" | Prepare and Update annually  
| align="left" | Prepare and Update annually  
| align="left" | 5
| align="center" | 5  
| align="center" | RO, MP, V  
| align="center" | RO, MP, V  
| align="center" | Colin, Sidrah
| align="center" | Colin, Sidrah
Line 51: Line 51:
| align="left" | IHE-RO Structure  
| align="left" | IHE-RO Structure  
| align="left" | Establish and publicize Terms of Reference, Position Terms, Succession planning  
| align="left" | Establish and publicize Terms of Reference, Position Terms, Succession planning  
| align="left" | 4
| align="center" | 4  
| align="center" | RO, MP, V  
| align="center" | RO, MP, V  
| align="center" |  
| align="center" |  
Line 57: Line 57:
| align="left" | Job Jar  
| align="left" | Job Jar  
| align="left" | Organize and maintain the job jar  
| align="left" | Organize and maintain the job jar  
| align="left" | 4
| align="center" | 4  
| align="center" | RO, MP, V  
| align="center" | RO, MP, V  
| align="center" |  
| align="center" |  
Line 63: Line 63:
| align="left" | PC and TC Membership and participation  
| align="left" | PC and TC Membership and participation  
| align="left" | Recruit volunteers for IHE-RO effort. Identify new stakeholders, and volunteers from other countries  
| align="left" | Recruit volunteers for IHE-RO effort. Identify new stakeholders, and volunteers from other countries  
| align="left" | 3
| align="center" | 3  
| align="center" | RO, MP, V, TC co-chairs  
| align="center" | RO, MP, V, TC co-chairs  
| align="center" |  
| align="center" |  
Line 69: Line 69:
| align="left" | Physician communication strategy and IHE-RO compliance  
| align="left" | Physician communication strategy and IHE-RO compliance  
| align="left" | Develop simple concise statement of “what does this mean to me in the clinic&nbsp;?”<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" | Develop simple concise statement of “what does this mean to me in the clinic&nbsp;?”<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" | 3
| align="center" | 3  
| align="center" | RO  
| align="center" | RO  
| align="center" |  
| align="center" |  
Line 75: Line 75:
| align="left" | IHE Communications  
| align="left" | IHE Communications  
| align="left" | Participate in IHE co-chair TCONs  
| align="left" | Participate in IHE co-chair TCONs  
| align="left" | 4
| align="center" | 4  
| align="center" | RO, MP, V  
| align="center" | RO, MP, V  
| align="center" | Sidrah, Bruce, rotate through PC co-chairs
| align="center" | Sidrah, Bruce, rotate through PC co-chairs
Line 81: Line 81:
| align="left" | Other IHE-RO country domains  
| align="left" | Other IHE-RO country domains  
| align="left" | Communicate with other IHE-RO country domains, e.g. Japan, Netherlands  
| align="left" | Communicate with other IHE-RO country domains, e.g. Japan, Netherlands  
| align="left" | 3
| align="center" | 3  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
|-
|-
| align="left" | FDA  
| align="left" | FDA  
| align="left" | Prepare white paper (details needed) USA specific.
| align="left" | Prepare white paper (details needed) USA specific.  
| align="left" | 2
| align="center" | 2  
| align="center" | RO  
| align="center" | RO  
| align="center" |  
| align="center" |  
Line 93: Line 93:
| align="left" | Publications and promotion  
| align="left" | Publications and promotion  
| align="left" | Organize all communications with RO community  
| align="left" | Organize all communications with RO community  
| align="left" | 3
| align="center" | 3  
| align="center" | MP  
| align="center" | MP  
| align="center" | Charles, Akkamma
| align="center" | Charles, Akkamma
Line 99: Line 99:
| align="left" | IHE Webinar  
| align="left" | IHE Webinar  
| align="left" | Prepare and give IHE Webinars  
| align="left" | Prepare and give IHE Webinars  
| align="left" | 1
| align="center" | 1  
| align="center" | Publications  
| align="center" | Publications  
| align="center" | Colin, Bruce
| align="center" | Colin, Bruce
|-
|-
| align="left" | Connectathon results  
| align="left" | Connectathon results  
| align="left" | Publicize results (via IHE-RO helper)
| align="left" | Publicize results (via IHE-RO helper)  
| align="left" | 3
| align="center" | 3  
| align="center" | RO, MP
| align="center" | RO, MP  
| align="center" | Bruce
| align="center" | Bruce
|-
|-
| 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" | 1
| align="center" | 1  
| align="center" | MP  
| align="center" | MP  
| align="center" |  
| align="center" |  
Line 119: Line 119:
*TDW-II  
*TDW-II  
*QAPV
*QAPV
| align="left" | 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)  
 
| align="left" | 3
| align="left" | 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)  
| align="center" | 3  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 126: Line 127:
| align="left" | SAM  
| align="left" | SAM  
| align="left" | Prepare content for SAM  
| align="left" | Prepare content for SAM  
| align="left" | 2
| align="center" | 2  
| align="center" | RO  
| align="center" | RO  
| align="center" | Kevin, Tony, Ramesh, Akkamma, Colin, Rishabh
| align="center" | Kevin, Tony, Ramesh, Akkamma, Colin, Rishabh
Line 132: Line 133:
| 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" | 3
| align="center" | 3  
| align="center" | RO, Publications  
| align="center" | RO, Publications  
| align="center" |  
| align="center" |  
Line 138: Line 139:
| 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" | 3
| align="center" | 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
Line 144: Line 145:
| align="left" | Use Case Follow-up  
| 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" | 2
| align="center" | 2  
| align="center" | MP, V  
| align="center" | MP, V  
| align="center" |  
| align="center" |  
Line 150: Line 151:
| 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" | 3
| align="center" | 3  
| align="center" | MP  
| align="center" | MP  
| align="center" | Rishabh (short term),&nbsp;?? (long term)
| align="center" | Rishabh (short term),&nbsp;?? (long term)
Line 156: Line 157:
| 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" | 3
| align="center" | 3  
| align="center" | MP  
| align="center" | MP  
| align="center" | Lakshmi
| align="center" | Lakshmi
Line 162: Line 163:
| align="left" | Wiki  
| align="left" | Wiki  
| align="left" | keep it up to date  
| align="left" | keep it up to date  
| align="left" | 2.5
| align="center" | 2.5  
| align="center" | MP  
| align="center" | MP  
| align="center" | Colin, Sidrah
| align="center" | Colin, Sidrah
Line 168: Line 169:
| 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" | 3
| align="center" | 3  
| align="center" | V, 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&nbsp;? Could be tied to RT Process flowchart. Should be this be dealt with as a use case ?
| align="left" | Develop Use Case, vision to include long term goal of providing a patient archive with patient access. EMR requirements&nbsp;? Could be tied to RT Process flowchart. Should be this be dealt with as a use case&nbsp;?  
| align="left" | 1
| align="center" | 1  
| align="center" | MP  
| align="center" | MP  
| align="center" |  
| align="center" |  
Line 180: Line 181:
| 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" | 3
| align="center" | 3  
| align="center" | MP  
| align="center" | MP  
| align="center" |  
| align="center" |  
Line 186: Line 187:
| 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" | 4
| align="center" | 4  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 192: Line 193:
| 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" | 2
| align="center" | 2  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 198: Line 199:
| align="left" | ESTRO Connectathon&nbsp;?  
| align="left" | ESTRO Connectathon&nbsp;?  
| align="left" | Will we have a presence at ESTRO&nbsp;?  
| align="left" | Will we have a presence at ESTRO&nbsp;?  
| align="left" | 4
| align="center" | 4  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 204: Line 205:
| 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" | 2
| align="center" | 2  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 210: Line 211:
| align="left" | Closing the Loop  
| align="left" | Closing the Loop  
| align="left" | Ensure vendors release products&nbsp; into the RO market within a certain time period from when the products passed at a Connectathon  
| align="left" | Ensure vendors release products&nbsp; into the RO market within a certain time period from when the products passed at a Connectathon  
| align="left" | 3
| align="center" | 3  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 216: Line 217:
| 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" | 4
| align="center" | 4  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 222: Line 223:
| 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" | 4
| align="center" | 4  
| align="center" | V  
| align="center" | V  
| align="center" |  
| align="center" |  
Line 228: Line 229:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 234: Line 235:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 240: Line 241:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 246: Line 247:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 252: Line 253:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 258: Line 259:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 264: Line 265:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 270: Line 271:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
Line 276: Line 277:
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="left" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
| align="center" |  
|}
|}


<br>
<br>  
 
[[Category:RO]]
[[Category:RO]]

Revision as of 11:02, 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

5 - Highest Priority, Secretariat
4 - Higher Priority, PC Co-chair leadership
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 5 RO, MP, V Sidrah
IHE Vision Document Prepare and Update annually 5 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
  • DPDW
  • TDW-II
  • QAPV
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