Quality, Research and Public Health

From IHE Wiki
Jump to navigation Jump to search

IHE Quality, Research and Public Health Domain (QRPH) addresses the infrastructure and content necessary to:

  • share information relevant to quality improvement,
  • improve the liaison between the primary care system and clinical research and
  • 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 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

QRPH is sponsored by Healthcare Information and Management Systems Society (HIMSS) and the Radiological Society of North America (RSNA) and manages the Quality Profiles.

There are two committees. For details regarding activities of each, select the appropriate link below:


Timeline: 2011-2012 Development Cycle

The Timeline shows the Domain Milestones of the developoment 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.

[All times in Central US time]

Timeline : 2010-2011 Development Cycle

The Timeline shows the Domain 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.

[All times in Central US time]

Timeframe Activity Scheduled Location
2011
July Profile Development for Public Comment Publication (Technical Committee) July 18-22 Oak Brook, IL (RSNA HQ)
May Profile Development for Trial Implementation Publication (Technical Committee) May 2-6 Oak Brook, IL (RSNA HQ)
February Profile Development for Public Comment Publication (Technical Committee) Feb. 7-10 Toronto, Canada
2010
November Initial Profile Development (Technical Committee) Nov. 17-18 Arlington, VA
October Profile Proposal Review and Work Planning (Planning Committee) Oct. 20-21 Oak Brook, IL (RSNA HQ)
Aug. Documents Published for Trial Implementation
July Public Comment Deadline
June Documents Published for Public Comment

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

See the respective committee pages for agenda and minutes of each meeting or tcon.

Supporters and Endorsements

IHE Quality, Research & Public Health (QRPH) is supported or endorsed by the following organizations:

Committee Rosters

Committee Distribution Lists

Subscribe to the QRPH domain committee lists by visiting the Google Group sites linked below:


Change Proposals

The QRPH specific CP Process:

The following text explains what the process used by the QRPH commitee in processing submitted CPs. It is consistent with the general IHE CP process and is informative only.

  1. Submission into the Incoming Directory. This is typically done via an email to the QRPH Technical Committee co-chair in charge of CPs (currently Jason Colquitt) or by directly updating the directory if you have access to the ftp write password.
  2. First consideration by the committee. If CP is accepted it is given a CP #, assigned an editor, renamed to CP-QRPH-xxxx-00.doc and placed in Assigned Directory. If CP is rejected it is moved to Rejected Directory 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.
  3. CP numbering is managed on the Change Proposal Master List page
  4. Committee works with editor to draft the CP. Versions are kept in Assigned directory and numbered -00, -01, -02, etc.
  5. Committee decides CP is ready for ballot. Latest version of CP is moved to Completed Directory and old versions are moved to Old-Versions Directory.
  6. Co-chair collects Completed CPs into a ballot. The Ballots Directory will be used for this.
  7. Ballot is released to the general community for voting
  8. Votes and comments are collected. All yes votes means the CP passed ballot and moved to Final Text Directory. 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.

Also see:

Timeframe Activity Scheduled Location
2011