|
|
| (323 intermediate revisions by 12 users not shown) |
| Line 1: |
Line 1: |
| IHE Quality, Research and Public Health Domain (QRPH) addresses the infrastructure and content necessary to share information relevant to quality improvement in electronic patient care and health care records, improves the liaison between the primary care system and clinical research and it serves in cases where population base surveillance is needed. The three components addressing the different aspects of the QRPH domain have all in common the secondary or the repurposing of data. | | IHE Quality, Research and Public Health Domain (QRPH) addresses the infrastructure and content necessary to: |
| * Quality – Repurposing of data
| | * share information relevant to quality improvement, |
| * Clinical Research – Secondary use of data
| | * improve the liaison between the primary care system and clinical research and |
| * Public Health – Population base surveillance
| | * provide population base health surveillance. |
| | The three distinct components of the QRPH domain are all reliant on the secondary use of data gathered in clinical care. |
|
| |
|
| The QRPH work enables the stakeholders to focus on the workflow cycle of queries for data and selection of population cohorts from within the clinical record. In addition, the QRPH incorporates the output from the query specification within the clinical system workflow to enable clinical decision support and defines profiles for adverse event reporting especially with reference to medication-related adverse outcomes. | | The work of QRPH enables the stakeholders to focus on the workflow cycle of queries for data and selection of population cohorts from within the clinical record. In addition, QRPH incorporates the output from the query specification within the clinical system workflow to enable clinical decision support and defines profiles for adverse event reporting, especially with reference to medication-related adverse outcomes. |
|
| |
|
| | | ==Sponsors and Committee Rosters== |
| It is sponsored by the [http://www.americanheart.org American Heart Association (AHA)], [http://www.himss.org Health Information Management Systems Society (HIMSS)], and [http://www.rsna.org Radiological Society of North America (RSNA)] and manages the [[Profiles#IHE Quality Profiles| Quality Profiles]] and the [[Frameworks| Quality Technical Framework]].
| | QRPH is sponsored by [http://www.himss.org Healthcare Information and Management Systems Society (HIMSS)] and the [http://www.rsna.org Radiological Society of North America (RSNA)] and manages the [http://wiki.ihe.net/index.php/Profiles#IHE_Quality.2C_Research.2C_and_Public_Health_Profiles Quality Profiles]. |
|
| |
|
| There are two committees. For details regarding activities of each, select the appropriate link below: | | There are two committees. For details regarding activities of each, select the appropriate link below: |
| * '''The [[Quality, Research and Public Health Planning Committee]]''' | | * '''The [[Quality, Research and Public Health Planning Committee]]''' |
| * '''The [[Quality, Research and Public Health Technical Committee]]''' | | * '''The [[Quality, Research and Public Health Technical Committee]]''' |
| | * '''[https://docs.google.com/spreadsheets/d/1phMzQQi3GKBz1LsDRYo1SB6iCctiie2ZXIbBrALjOME/edit?usp=sharing QRPH Planning and Technical Committee Rosters] |
|
| |
|
|
| |
|
| __TOC__ | | __TOC__ |
|
| |
|
| ==Timeline : 2009-2010 Development Cycle== | | ==QRPH Development Continuous Cycle== |
| The Timeline shows the '''main milestones''' of the development cycle, the '''Timeframe''' when they are typically expected to happen, and the actual date/time/location they have been '''Scheduled''' for this year. | | The Quality, Research and Public Health Committee has moved to a continuous development cycle. The three 4-day face-to-face working meetings in the first half of the calendar year, plus two 2-day selection meetings in the last calendar quarter, are replaced by four 4-day working meetings evenly spaced through the year. A portion of each meeting is devoted to planning tasks such as review and prioritizing of proposals, and the rest of the meeting would operate similar to our current technical meetings, except each work item could be in a different phase (volume 1 prep, public comment prep, TI prep). |
| | |
| | [https://wiki.ihe.net/index.php/QRPH_Continuous_Development_Cycle Additional process details can be found here.] |
| | |
| | ==Planning and Development Cycle== |
|
| |
|
| '''Specific meetings''' and their agendas and minutes are generally listed on the page of the relevant Committee.
| | This Domain is currently meeting jointly with the Patient Care Coordination (PCC) Domain. Weekly calls are held Thursdays 11:00am CT. Meeting information and Agendas are *[https://docs.google.com/spreadsheets/d/1Ts2gJUJZXlFt3QfrLD3HeuLgYv-NRlZcu9_Q8_XdRYo/edit?usp=sharing Here]. |
| | |
| | The following outlines the general activities and steps planned for the QRPH Continuous development cycle. |
|
| |
|
| [''All times in Central US time'']
| |
|
| |
|
| {| style="width:100%" border="1" cellpadding="3" | | {| style="width:100%" border="1" cellpadding="3" |
| ! Timeframe | | ! Schedule |
| ! Activity | | ! Activity |
| ! Scheduled
| |
| ! Location
| |
| |- | | |- |
| | colspan="4" align="center" style="background:#dddddd" | '''2010''' | | | colspan="4" align="center" style="background:#dddddd" | '''2025''' |
| |- | | |- |
| | Aug. | | | Continuous Development |
| | Documents Published for Trial Implementation | | | Call for Profile/White Paper Proposals Announced (one month before scheduled planning committee face to face or virtual meeting) |
| | |- |
| | | Continuous Development |
| | | Profile Proposals Due to Planning Co-Chairs |
| | |- |
| | | July 14-17, 2025 Face-to-Face RSNA Headquarters Oak Brook, IL |
| | | IHE ITI, PCC/QRPH Domain Continuous Development Meeting |
| | |- |
| | | colspan="4" align="center" style="background:#dddddd" | '''2026''' |
| | |- |
| | | | | |
| | | | | |
| |- | | |- |
| | July
| |
| | Public Comment Deadline
| |
| | | | | |
| | | | | |
| |-
| |
| | June
| |
| | Documents Published for Public Comment
| |
| |
| |
| |
| |
| |-
| |
| | colspan="4" align="center" style="background:#dddddd" | '''2009'''
| |
| |- | | |- |
| | Dec.
| |
| | Select Final Profiles
| |
| | | | | |
| | | | | |
| |- | | |- |
| | Nov. | | | Continuous Development |
| | QRPH Technical/Planning Committee Face-to-Face Meeting | | | Publication of Final Text Technical Framework |
| | Nov 10-11
| |
| | RSNA Headquarters, Oakbrook, IL
| |
| |- | | |- |
| | Oct. | | | colspan="4" align="center" style="background:#dddddd" | '''2027''' |
| | QRPH Planning Committee Face-to-Face Meeting | |
| | Oct 5-6
| |
| | RSNA Headquarters, Oakbrook, IL
| |
| |- | | |- |
| | Oct. | | | |
| | QRPH Planning Webinar #4 (joint with PCC) | | | |
| | Oct 1<br>11:00-1:00pm CT (Tentative)
| |
| |
| |
| |- | | |- |
| | Sept. | | | |
| | QRPH Planning Webinar #3 (joint with PCC)
| |
| | Sept 29<br>3:00-5:00pm CT
| |
| |
| |
| |-
| |
| | Sept.
| |
| | QRPH Planning Webinar #2
| |
| | Sept 25<br>10:00-12:00pm CT
| |
| |
| |
| |-
| |
| | Sept.
| |
| | QRPH Planning Webinar #1
| |
| | Sep 23<br>1:00-3:00pm CT
| |
| |
| |
| |-
| |
| | Sept.
| |
| | Deadline for submission of new QRPH Profile proposals
| |
| | Sept 15<br>at 11:59 pm CT
| |
| |
| |
| |}
| |
| | |
| ==Timeline : 2008-2009 Development Cycle==
| |
| The '''Timeline shows the main milestones''' of the development cycle, the '''Timeframe''' when they are typically expected to happen, and the actual date/time/location they have been '''Scheduled''' for this year. '''Specific meetings''' and their agendas and minutes are generally listed on the page of the relevant Committee.
| |
| [ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Meetings/2008_Nov18_19/2009%20QRPH%20Timeline.pdf 2008-2009 Timeline]
| |
| [''All times in Central US time'']
| |
| | |
| {| style="width:100%" border="1" cellpadding="3"
| |
| ! Timeframe
| |
| ! Activity
| |
| ! Scheduled
| |
| ! Location
| |
| |-
| |
| | colspan="4" align="center" style="background:#dddddd" | '''2010'''
| |
| |-
| |
| | Jan.
| |
| | Test implementations at Connectathon
| |
| |
| |
| | Chicago
| |
| |-
| |
| | colspan="4" align="center" style="background:#dddddd" | '''2009'''
| |
| |-
| |
| | Aug
| |
| | Documents Published for Trial Implementation
| |
| | Aug. 10
| |
| | | | | |
| |- | | |- |
| | July.
| |
| | QRPH Technical Committee Face-to-Face Meeting - Resolution of Public Comments and Preparation of Documents for Publication [[Agenda July 13-17 2009 QRPH Tech|Agenda]]
| |
| | July 13-17
| |
| | RSNA Headquarters, Oakbrook, IL
| |
| |-
| |
| | June
| |
| | Public Comment Deadline
| |
| | | | | |
| | | | | |
| |- | | |- |
| | June | | | Continuous Development |
| | Documents Published for Public Comment
| |
| | June 1
| |
| | | | | |
| |- | | |- |
| | May. | | | Continuous Development |
| | QRPH Technical Committee Face-to-Face Meeting - Completion of Documents for Public Comment [[Agenda May 4-8 2009 QRPH Tech|Agenda]] | | | |
| | May 4-8
| |
| | RSNA Headquarters, Oakbrook, IL
| |
| |- | | |- |
| | Apr.
| |
| | European Union Connectathon
| |
| | April 20-24
| |
| |
| |
| |- | | |- |
| | Apr. | | | colspan="4" align="center" style="background:#dddddd" | '''2028''' |
| | HIMSS 2009 | |
| | April 6 - 9
| |
| | Chicago, IL
| |
| |- | | |- |
| | Feb. | | | |
| | North American Connectathon | | | |
| | February 23 - 27
| |
| | Chicago, IL
| |
| |- | | |- |
| | Jan. | | | |
| | QRPH Technical Committee Face-to-Face Meeting [[Agenda Jan 26-29 2009 QRPH Tech|Agenda]] | | | IHE ITI, PCC, QRPH Domain Continuous Development Meeting |
| | January 26-29
| |
| | RSNA Headquarters, Oakbrook IL
| |
| |- | | |- |
| | colspan="4" align="center" style="background:#dddddd" | '''2008''' | | | |
| | | |
| |- | | |- |
| | Dec. | | | Continuous Development |
| | Joint Planning/Technical Committee TConn to Select Final Profiles | | | |
| <br>[[Agenda QRPH Joint Planning/Technical TCon 22 Dec 2009]]
| |
| | Dec 22 12:00 - 2:00 PM CST
| |
| | Tcon<br>[https://ihe.webex.com/ihe/j.php?J=923769790 WebEx Link]
| |
| |-
| |
| | Nov.
| |
| | QRPH Technical Committee Face-to-Face Meeting<br>
| |
| [[Agenda Nov 18-19 QRPH Tech|Agenda]]<br>
| |
| Selected Profiles Detailed at:[[Quality, Research and Public Health Technical Committee]]
| |
| | Nov 18-19
| |
| | RSNA Headquarters, Oakbrook IL
| |
| |-
| |
| | Oct.
| |
| | QRPH Planning Committee Face-to-Face Meeting<br>
| |
| [[QRPH Plan Agenda 2008.10.20-21|Agenda]]<br>
| |
| [[Quality Plan Minutes 2008.10.20-21|Minutes]]
| |
| | Oct 20-21
| |
| | Arlington VA HIMSS Office
| |
| |- | | |- |
| | |
| |} | | |} |
|
| |
|
| ==Roadmap==
| |
|
| |
|
| The '''[[Quality Roadmap]]''' outlines goals and plans over the next 5 years. The Roadmap will be updated after the Quality, Research & Public Health Domain (QRPH) March 11-14, 2008 Technical Committee meeting.
| |
|
| |
|
| ==Minutes== | | *[https://docs.google.com/spreadsheets/d/1Ts2gJUJZXlFt3QfrLD3HeuLgYv-NRlZcu9_Q8_XdRYo/edit?usp=sharing QRPH Domain Cycle Planning and Technical Development Agendas] |
|
| |
|
| See the respective committee pages for agenda and minutes of each meeting or tcon.
| | *Older Schedules |
| * The [[Quality, Research and Public Health Planning Committee]] | | **[[QRPH 2018-2019 Planning and Development Cycle (calendar year 2017-2018)]] |
| * The [[Quality, Research and Public Health Technical Committee]] | | **[[QRPH 2017-2018 Planning and Development Cycle (calendar year 2016-2017|QRPH 2017-2018 Planning and Development Cycle (calendar year 2016-2017)]] |
| | **[[QRPH 2016-2017 Planning and Development Cycle (calendar year 2015-2016)]] |
|
| |
|
| ==Profile Selection Current Cycle 2008-2009==
| | __TOC__ |
|
| |
|
| '''The following proposals have been evaluated by the Planning and Technical Committees. Final resolution is pending a Planning and Technical Conference Call on December 22, 2008 (see calendar for details).'''
| | ==Change Proposals== |
| * [ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/IHE_QRPH_Chronic_Disease_Management_Reporting_v2.doc Chronic Disease Management Reporting]
| |
| ** Profile Approved - Review by Dec 22 regarding consolidation with Diabetes Care Management
| |
| * [[Retrieve Protocol for Execution]]
| |
| ** [[Detailed Proposal]]
| |
| ** Profile Approved in Technical Committee
| |
| *[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/Maternal_and_child_health.doc Maternal child health]
| |
| ** [ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/maternal_v_detailed%20proposals%20nov%20f2f.ppt Maternal and Child Health Proposal Powerpoint]
| |
| ** [ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/1st%20certificate.rtf Maternal and Child Health First Certificate]
| |
| ** Profile Approved in Technical Committee
| |
| *[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/IHE_Profile_Proposal_Diabetes%20Care%20Mngt%2011-18-08.doc Diabetes Care Management]
| |
| ** White Paper Approved in Technical Committee - Review by Dec 22 regarding consolidation with Chronic Disease Management Reporting
| |
| * [ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/Performance%20Query%20Request%20Structure.doc Performance Quality Report]
| |
| ** Profile Approved in Technical Committee
| |
| *[ftp://ftp.ihe.net/Quality/2009_2010_YR_3/Technical/Detailed_Proposals/IHE_Profile_Proposal_Newborn_Screening_11-18-08.doc New-born screening] (This is a Planning White Paper)
| |
| ** Planning White Paper
| |
| * Pseudonymization White Paper under consideration by QRPH Planning Committee
| |
|
| |
|
| | __NOTOC__ |
|
| |
|
| ==2007-2008 Activity==
| | The Quality Research and Public Health domain committee follows the general IHE [[Change Proposal Process]]. QRPH specific details are listed below: |
| | |
| The Quality, Research & Public Health Domain (QRPH) is currently focused on the workflow cycle of queries for data and selection of population cohorts from within the clinical record. The cycle begins with a query defintion that can be incorporated into the EHR to identify appropriate patients that represent the desired cohort, and identify expected interventions as well as exceptions that would exclude individuals from the cohort. Cohort selection and management should be enabled for concurrent management and analysis as well as for retrospective analysis. Methods for accessing patient-level clinical data to meet the requirements of the query were discussed in the framework reviewed in 2007 (Patient-Level Export of Quality Data <PEQD>). The 2008 work effort completed two profiles and one white paper. | |
| * [[Performance Measurement Data Element Structured for EHR Extraction]] White Paper * [ftp://ftp.ihe.net/Quality/2008_2009_YR_2/Technical/CLEAN%20IHE_QRPH_Whitepaper_Perfomance_Measure_Data_Element_Structured_for_EHR_Extraction_2008-07-22_Comment_resolution.doc Final Version]
| |
| * [[Drug Safety Content]] Profile
| |
| * [[Clinical Research Data Capture]]
| |
| | |
| The QRPH Domain continues to seek volunteers for participation in current work effort, change proposals to existing profiles, and recommendations for new activities. If you would like to participate, contact the [http://wiki.ihe.net/index.php?title=Quality_Planning_Committee QRPH Planning Committe] or the [http://wiki.ihe.net/index.php?title=Quality%2C_Research_and_Public_Health_Technical_Committee QRPH Technical Committee].
| |
| | |
| == IHE Quality, Research and Public Health Domain (QRPH): A Call for Participation ==
| |
| | |
| The Domain began under the sponsorship of the American College of Cardiology (ACC), the American Heart Association (AHA), the Healthcare Information and Management Systems Society (HIMSS), and the Radiological Society of North America (RSNA) as outreach to Clinician Communities to Discuss How to Incorporate Quality Guidelines into Electronic Health Record Interoperability. Its mission is to address the infrastructure necessary to share information relevant to quality improvement in electronic patient care and health care records. Beginning with a domain kickoff meeting April 11-12 2007 at the Four Points Sheraton, Chicago-O'Hare. The meeting focused on developing use cases to provide the basis for a Technical Framework to enable sharing of quality guidelines in electronic health record (EHR) applications and related systems.
| |
| | |
| Understanding the similarities for repurposing data for Quality, Research & Public Health, the Domain scope incorporates the broader vision. Clinical, demographic and financial information about individuals is used routinely in the process of providing clinical care directly to patients. Information gained through direct care processes provided to patients has significant value with respect to the monitoring of disease patterns for known clinical processes regarding incidence, prevalence and situational awareness, and to the identification of new patterns of disease not previously known or anticipated. Public Health requirements therefore, are met through the re-purposing of clinically derived data for analysis. Such data are subsequently incorporated within existing Public Health population analyses and programs for direct outreach and condition management through registries and locally determined appropriate treatment programs or protocols. Similarly, information about care processes delivered to patients is used to identify adherence to expected evidence-based clinical care protocols or guidelines to determine the processes and/or outcomes that determine the quality of care provided by individual clinicians or groups of clinicians. Much of the data required for quality analyses exists within the clinical patient record and, similar to the examples provided for Public Health, those data can be re-purposed for analysis. The protocols for subsequent management of clinicians and individual patients with respect to quality data are often addressed as performance improvement or performance management or disease management initiatives on the level of populations and for individual patient care. Research and clinical trials, likewise, require identification of patterns of clinical presentation and processes to identify individual patients and groups of patients appropriate to consider for inclusion in research protocols and for whom consent might be sought. Subsequent management, follow up and clinical information requirements require similar infrastructure and high level content gathering capabilities as identified in Quality and Public Health. Hence, there are significant similarities among Quality, Research & Public Health requirements for re-purposing of existing clinical data and the subsequent management of patients and clinical care providers. The issues of specifications for patient selection, and for individual and aggregate (summary) reporting of data, and for privacy and security constraints for re-use (or secondary use) of patient or clinician-derived data can best be managed in an IHE Domain specifically focused in this area. Such a domain also provides focus where Quality, Research & Public Health experts can collaborate and coordinate activities. Globally there is a need to gather and report on secondary data used in public health, clinical decision support and research to improve quality, efficiency and safety of patient care delivery.
| |
| | |
| | |
| Current sponsors include the American Heart Association (AHA), the Healthcare Information and Management Systems Society (HIMSS), and the Radiological Society of North America (RSNA).
| |
| | |
| ==Supporters and Endorsements==
| |
|
| |
|
| IHE Quality, Research & Public Health (QRPH) is supported or endorsed by the following organizations:
| | * CPs should be developed using the [http://wiki.ihe.net/images/1/14/IHE_Change_Proposal-Template-V10.1.docx standard change proposal template]. |
| | * Submit incoming CP's to the [ftp://iheyr2@ftp.ihe.net/Quality/TF_Maintenance/CPs/01%20Submitted/ Submitted Directory]. You may choose to do so in one of two ways: |
| | *# E-mail the QRPH Technical Committee co-chair in charge of CPs (check [[Committees]] for current co-chair - subject the e-mail as "New QRPH CP") |
| | *# Directly update the directory if you have access to the ftp write password and e-mail the QRPH co-chairs to let them know of the new CP. |
| | * The CPs are tracked on a Google Docs spreadsheet [https://docs.google.com/spreadsheet/ccc?key=0AlA2kOz33tdvdEdzQjE3cnJMSU1pVnZDX0tpTDdLb1E&hl=en_US Change Proposals]. |
|
| |
|
| * [http://www.americanheart.org American Heart Association (AHA)]
| |
| * [http://www.himss.org Health Information Management Systems Society (HIMSS)]
| |
| * [http://www.RSNA.org Radiological Society of North America]
| |
|
| |
| ==Committee Rosters==
| |
| * [ftp://ftp.ihe.net/Quality/ROSTER_QRPH QRPH Planning Roster]
| |
| * [ftp://ftp.ihe.net/Quality/ROSTER_QRPH QRPH Technical Roster]
| |
|
| |
|
| ==Committee Distribution Lists== | | ==Committee Distribution Lists== |
| Subscribe to the QRPH domain committee lists by visiting the Google Group sites linked below: | | Subscribe to the QRPH domain committee lists by visiting the Google Group sites linked below: |
|
| |
|
| *[http://groups.google.com/group/iheqrphtech QRPH Technical Committe Google Group] | | *[http://groups.google.com/group/iheqrphtech QRPH Technical Committee Google Group] |
| *[http://groups.google.com/group/iheqrphplan QRPH Planning Committe Google Group ] | | *[http://groups.google.com/group/iheqrphplan QRPH Planning Committee Google Group] |
| | | *[[QRPH Archive]] |
| ==See Also==
| |
| | |
| | |
| The [[Quality, Research and Public Health Planning Committee]]
| |
| The [[Quality, Research and Public Health Technical Committee]]
| |
| | |
| ==Change Proposals==
| |
| __NOTOC__
| |
| ==='''Also see:'''===
| |
| * [[Change Proposal Process | IHE Change Proposal Process]] | |
| * [[PCC_Change_Proposals | PCC Change Proposal Process]]
| |
| * [[PCC_Change_Proposal_Master_List | PCC Change Proposal Master List]]
| |
| * [[PCC_Change_Proposal_Tracking | PCC Change Proposal Tracking]]
| |
| | |
| | |
| | |
| ==The PCC specific CP Process ==
| |
| The following text explains what the process used by the ITI commitee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.
| |
| | |
| # Submission into the [ftp://ftp.ihe.net/Patient_Care_Coordination/Maintenance2009/CPs/Incoming Incoming] directory. This is typically done via an email to the PCC Technical Committee co-chair in charge of CPs (currently Tone Southerland) or by directly updating the directory if you have access to the ftp write password.
| |
| # First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-PCC-xxxx-00.doc and placed in Assigned. If CP is rejected it is moved to Rejected and submitter is informed of explanation for rejection. Likely reasons for rejection are: duplicate, merged, withdrawn or not enough information to understand the request. Rejected CPs can be resubmitted with more information for reconsideration.
| |
| # CP numbering is managed on the [[PCC_Change_Proposal_Master_List | Change Proposal Master List page]]
| |
| # Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
| |
| # Committee decides CP is ready for ballot. Latest version of CP is moved to Completed diretory and old versions are moved to old_versions.
| |
| # Co-chair collects Completed CPs into a ballot. The Ballot directory will be used for this.
| |
| # Ballot is released to the general community for voting
| |
| # Votes and comments are collected. All yes votes means the CP passed ballot and moved to FinalText. No votes are resolved by the committee. Sometimes CP is withdrawn, sometimes NO voter changes to yes vote after explanations. CP may be updated in this process. If updates are insignificant (clarification only) the CP is considered passed. If updates are significant the CP is submitted for another ballot.
| |
| # CP approved in ballot are put in FinalText and scheduled to be integrated into the Technical Framework or Supplement.
| |
|
| |
|
| == Directory Structure on FTP == | | ==Testing Discussion and Notes== |
| * The following directory structure is used to manage CPs that are submitted as word documents.
| |
| ** '''Assigned:''' contains CPs that have been assigned an editor and are being actively worked on by the committee, i.e. Assigned status
| |
| ** '''Ballots:''' contains Ballots that have been released for voting by the general community
| |
| ** '''Cancelled:''' contains CPs that have been cancelled
| |
| ** '''Completed:''' contains the last version of a CP that is in Completed status. It is waiting to be put in a ballot
| |
| ** '''Incoming:''' contains CPs which have been submitted but have not been assigned a CP number or an editor. This is the place that new incoming CPs are placed prior to the first stage of processing by the committee.
| |
| ** '''Incorporated:''' contains the version of the CP that was integrated into the TF.
| |
| ** '''Rejected:''' CPs that have been submitted by rejected by the committee
| |
|
| |
|
| This page is based on the [[Domain Template]].
| | *[[VRDR Testing]] |