Difference between revisions of "Technical Confirmation Process"
Jump to navigation
Jump to search
| (14 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{TOCright}} | ||
| + | ==Planning== | ||
| − | + | <Details TBA> | |
| − | |||
| − | A procedure is outlined below listing what is done (by whom). | + | ==Soliciting Feedback== |
| + | This step collects feedback on use of the document by implementers and users in the field, including clinical oncologists, imaging scientists, pharma, CRO’s, etc. | ||
| + | |||
| + | Whereas the review and public comment steps prior to this focused on the document itself, this step now seeks feedback on how well it works in practice. As such, comments are solicited specifically from those that have used it and only those that have used it. | ||
| + | |||
| + | A procedure is outlined below listing what is done ('''by whom'''). | ||
Period: 30 days | Period: 30 days | ||
| − | * Collect list of people that have participated in the field test ( | + | * Collect list of people that have participated in the field test ('''Field Test Leader''') |
| − | * Finalize comment form that will be used in the survey ( | + | * Finalize comment form that will be used in the survey ('''RSNA Staff/Technical Committee''') |
| − | * | + | ** ''<Q. What's the relationship between this comment form and the standard form linked below?>'' |
| − | ** | + | ** ''<Add guidance for the need to achieve full coverage, and guidance for doing that over multiple sites - prefer 3 site viewpoints - may split over additional sites to cover breadth of profile (e.g. if multiple organs are addressed in a single profile, the practicality might differ for each)>'' |
| − | ** | + | ** ''Document the coverage of the requirements. If coverage is incomplete, can reduce scope of profile or document rationale'' |
| − | * Email | + | ** Q If a TC Tester completes the profile, can they be registered? If the profile requirements don't get changed, yes. |
| − | + | * Announce Call for Feedback to mailing lists ('''RSNA Staff'''), including | |
| − | + | ** link to the document | |
| − | * Collate all comments into a spreadsheet ( | + | ** link to the [[:Media:QIBA_User_Feedback_Template-2011.01.doc | QIBA Trial Implementation Feedback Template]] |
| − | * | + | * Email completed Feedback Template to Field Test leader ('''Commenters''') |
| − | * | + | * Collate all Feedback comments into a '''Feedback Resolution spreadsheet''' ('''RSNA Staff/Field Test Leader''') |
| − | * | + | * Additionally, summarize feedback into a report ('''Field Test Leader'''). |
| − | + | * Review comments, making changes to the document as needed ('''Technical Committee''') | |
| − | + | * Record comment resolutions in spreadsheet | |
| + | * Vote on next step for the document ('''Technical Committee'''), either: | ||
| + | ** refer the document to the Modality Committee for Final Text publication | ||
| + | ** conduct another round of field test on revised document | ||
| + | ** place the document into inactive status | ||
| + | * Post '''Feedback Resolution spreadsheet''', revised document to the '''[[Comment Resolutions|Wiki]]''' ('''Field Test Leader/RSNA Staff) | ||
==Feedback after Publication== | ==Feedback after Publication== | ||
The purpose of this process step is to actively seek and periodically respond to feedback on use of published documents. It is important to put this into context with other activities that may seem similar at first: Whereas the review and public comment steps that are part of the Drafting phase focus on the document itself, prior to its use, and the Collect Feedback step as part of the Field Test phase collects feedback on the initial use of the document given that it has been placed into trial implementation, this step is where longer-term, extended use of the document allows for actual assessment of its performance in practice. That is, over the course of time clinical trials may complete that had been designed with this, and/or other results from field usage may become evident either with the user or supplier base. As such, comments are solicited periodically for a wide range of the public that may connect with it in some way. | The purpose of this process step is to actively seek and periodically respond to feedback on use of published documents. It is important to put this into context with other activities that may seem similar at first: Whereas the review and public comment steps that are part of the Drafting phase focus on the document itself, prior to its use, and the Collect Feedback step as part of the Field Test phase collects feedback on the initial use of the document given that it has been placed into trial implementation, this step is where longer-term, extended use of the document allows for actual assessment of its performance in practice. That is, over the course of time clinical trials may complete that had been designed with this, and/or other results from field usage may become evident either with the user or supplier base. As such, comments are solicited periodically for a wide range of the public that may connect with it in some way. | ||
| − | A procedure is outlined below listing what is done (by whom). | + | A procedure is outlined below listing what is done ('''by whom'''). |
Period: 30 days | Period: 30 days | ||
| − | * Periodically, collect list of people that may have used the document and/or professional societies that may have a particular relationship to the document ( | + | * Periodically, collect list of people that may have used the document and/or professional societies that may have a particular relationship to the document ('''RSNA Staff''') |
| − | * Finalize comment form that will be used in the survey ( | + | * Finalize comment form that will be used in the survey ('''RSNA Staff/Technical Committee''') |
| − | * Send announcement to mailing lists ( | + | * Send announcement to mailing lists ('''RSNA Staff''') |
** reminder copy of document that has been placed into field test | ** reminder copy of document that has been placed into field test | ||
** provide a link to the [[:Media:QIBA_Maintenance_Phase_Feedback_Template-2011.01.doc | QIBA User Feedback Template]] | ** provide a link to the [[:Media:QIBA_Maintenance_Phase_Feedback_Template-2011.01.doc | QIBA User Feedback Template]] | ||
| − | * Email comments to | + | * Email comments to RSNA Staff (Commenters) |
** commenters include full range of users of the document, e.g., vendors/suppliers, clinical oncologists, imaging scientists, pharma, CRO’s, etc. However, only people who have used document are included. | ** commenters include full range of users of the document, e.g., vendors/suppliers, clinical oncologists, imaging scientists, pharma, CRO’s, etc. However, only people who have used document are included. | ||
** please use the provided comment form | ** please use the provided comment form | ||
| − | * Collate all comments into a spreadsheet ( | + | * Collate all comments into a spreadsheet ('''RSNA Staff''') |
| − | ** Summarize range of feedback to the questions into a report for review by the technical committee provided by | + | ** Summarize range of feedback to the questions into a report for review by the technical committee provided by RSNA Staff. |
** Technical Committee decides what changes to make (if any) to the document and whether to refer it to the Modality Committee for re-publication of an updated version, whether to branch the document leaving the current version in place but spawning a derivative, or to retire the document | ** Technical Committee decides what changes to make (if any) to the document and whether to refer it to the Modality Committee for re-publication of an updated version, whether to branch the document leaving the current version in place but spawning a derivative, or to retire the document | ||
* Record resolution in spreadsheet | * Record resolution in spreadsheet | ||
** Regardless of recommended status for this document, ensure that the results are made available to related activities | ** Regardless of recommended status for this document, ensure that the results are made available to related activities | ||
Revision as of 20:56, 7 April 2020
Planning
<Details TBA>
Soliciting Feedback
This step collects feedback on use of the document by implementers and users in the field, including clinical oncologists, imaging scientists, pharma, CRO’s, etc.
Whereas the review and public comment steps prior to this focused on the document itself, this step now seeks feedback on how well it works in practice. As such, comments are solicited specifically from those that have used it and only those that have used it.
A procedure is outlined below listing what is done (by whom).
Period: 30 days
- Collect list of people that have participated in the field test (Field Test Leader)
- Finalize comment form that will be used in the survey (RSNA Staff/Technical Committee)
- <Q. What's the relationship between this comment form and the standard form linked below?>
- <Add guidance for the need to achieve full coverage, and guidance for doing that over multiple sites - prefer 3 site viewpoints - may split over additional sites to cover breadth of profile (e.g. if multiple organs are addressed in a single profile, the practicality might differ for each)>
- Document the coverage of the requirements. If coverage is incomplete, can reduce scope of profile or document rationale
- Q If a TC Tester completes the profile, can they be registered? If the profile requirements don't get changed, yes.
- Announce Call for Feedback to mailing lists (RSNA Staff), including
- link to the document
- link to the QIBA Trial Implementation Feedback Template
- Email completed Feedback Template to Field Test leader (Commenters)
- Collate all Feedback comments into a Feedback Resolution spreadsheet (RSNA Staff/Field Test Leader)
- Additionally, summarize feedback into a report (Field Test Leader).
- Review comments, making changes to the document as needed (Technical Committee)
- Record comment resolutions in spreadsheet
- Vote on next step for the document (Technical Committee), either:
- refer the document to the Modality Committee for Final Text publication
- conduct another round of field test on revised document
- place the document into inactive status
- Post Feedback Resolution spreadsheet, revised document to the Wiki (Field Test Leader/RSNA Staff)
Feedback after Publication
The purpose of this process step is to actively seek and periodically respond to feedback on use of published documents. It is important to put this into context with other activities that may seem similar at first: Whereas the review and public comment steps that are part of the Drafting phase focus on the document itself, prior to its use, and the Collect Feedback step as part of the Field Test phase collects feedback on the initial use of the document given that it has been placed into trial implementation, this step is where longer-term, extended use of the document allows for actual assessment of its performance in practice. That is, over the course of time clinical trials may complete that had been designed with this, and/or other results from field usage may become evident either with the user or supplier base. As such, comments are solicited periodically for a wide range of the public that may connect with it in some way.
A procedure is outlined below listing what is done (by whom).
Period: 30 days
- Periodically, collect list of people that may have used the document and/or professional societies that may have a particular relationship to the document (RSNA Staff)
- Finalize comment form that will be used in the survey (RSNA Staff/Technical Committee)
- Send announcement to mailing lists (RSNA Staff)
- reminder copy of document that has been placed into field test
- provide a link to the QIBA User Feedback Template
- Email comments to RSNA Staff (Commenters)
- commenters include full range of users of the document, e.g., vendors/suppliers, clinical oncologists, imaging scientists, pharma, CRO’s, etc. However, only people who have used document are included.
- please use the provided comment form
- Collate all comments into a spreadsheet (RSNA Staff)
- Summarize range of feedback to the questions into a report for review by the technical committee provided by RSNA Staff.
- Technical Committee decides what changes to make (if any) to the document and whether to refer it to the Modality Committee for re-publication of an updated version, whether to branch the document leaving the current version in place but spawning a derivative, or to retire the document
- Record resolution in spreadsheet
- Regardless of recommended status for this document, ensure that the results are made available to related activities