1 / 7

IRB Process as Internal Reviewer Of Interoperability Specifications

IRB Process as Internal Reviewer Of Interoperability Specifications. Dovetailing with the TC Restructuring and Process Implications. Current HITSP Process. 1 Month. 1 Month. 2-3 Months. 3 Months. 3 Months. Preliminary Use Case Analysis. Preliminary Project Plan. RDSS.

ally
Télécharger la présentation

IRB Process as Internal Reviewer Of Interoperability Specifications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IRB Process as Internal Reviewer Of Interoperability Specifications Dovetailing with the TC Restructuring and Process Implications

  2. Current HITSP Process 1 Month 1 Month 2-3 Months 3 Months 3 Months Preliminary Use Case Analysis Preliminary Project Plan RDSS Interoperability Specificatikon Inspection Test/ Public Comment RDSS Comments Preliminary Use Case Final Use Case 2-3 Months Maintenance Resolve and Disposition Comments Panel Approval, Public Release Implementors/SDO Feedback

  3. TC Restructuring and Workload Implications • Restructuring – TCs will have to collaborate • Perspective TCs will work on the IS • Domain TCs work on the supporting constructs • Expected Work Load • 6 new use cases • Completion of the current 4 ISs and S&P • Deferred work for all of the existing ISs (the current 4 and last year's 3) • NHIN/CCHIT • Other external needs We Need To Aggressively Pursue Reuse

  4. Restructuring Proposal Perspective Technical Committees Care Management and Health RecordsTechnicalCommittee Infrastructure, Security and Privacy Technical Committee Administrative and Financial TechnicalCommittee Population Perspective TC Provider Perspective TC Consumer Perspective TC Cross-TC Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Security & Privacy Workflow and Process Terminology And Knowledge Representation Messaging and Datatypes Modeling Domain Technical Committees - TC Leadership Oversight - Communications function Foundations Committee

  5. How Perspective and Domain TCs Would Work Together and with IRB, in sequence- as defined by TC Leadership on 1/4/08 • RDSS Development • Preliminary Use Case Analysis Perspective TC • Collaborate and Assess Assignment of Ownership to Perspective TC • Identify Broad areas of Domain TC Involvement • Project Plan – Perspective TC with review by Domain TC, IRB review point • Detailed Requirements Analysis - Perspective TC with Domain TC as needed • Assess possibility for Reuse/Repurpose of existing constructs - Perspective and Domain TC • Preliminary RDSS Design – Perspective TC, IRB review point • Identify New Constructs and allocate requirements Perspective and Domain TC • Finalize RDSS Design – Perspective TC, IRB review point • IS Development • Finalize requirements - concurrently • for IS - Perspective TC • for New Constructs for assigned Domain TC – Domain TC with Perspective TC - IRB, TC Leadership • New Construct Development, Standards Selection for New Construct– Domain TCIRB review point • Finalize constraints on constructs - Perspective TC • Interoperability Specification Writing and System Integration of Constructs - Perspective TC Color coding for the 3 major components (Perspective TC, Domain TC, and IRB). See Graphic on next page

  6. How Perspective and Domain TCs Would Work Together and with IRB, in sequence – some suggested “tweaks” to better portray IRB involvement • Initial Planning (IRB Review when complete) • Preliminary Use Case Analysis • TCs Collaborate to Assess and Assign Ownership to Perspective TC • Identify Broad areas of Domain TC Involvement - Perspective TC • Project Plan – Perspective TC with review by Domain TC • RDSS Development (IRB Review when complete) • Detailed Requirements Analysis - Perspective TC with Domain TC as needed • Assess possibility for Reuse/Repurpose of existing constructs - Perspective and Domain TC • Preliminary RDSS Design – Perspective TC (IRB, TC Leadership review point) • Identify New Constructs and allocate requirements Perspective and Domain TC • Finalize RDSS Design – Perspective TC • IS Development (IRB Review when complete) • Finalize requirements - concurrently (IRB, TC Leadership Review when complete) • for IS - Perspective TC • for New Constructs for assigned Domain TC – Domain TC with Perspective TC - • New Construct • Development, Standards Selection for New Construct– Domain TC • Finalize constraints on constructs - Perspective TC • Interoperability Specification Writing and System Integration of Constructs - Perspective TC Color coding for the 3 major components (Perspective TC, Domain TC, and IRB). See Graphic on next page

  7. Revised HITSP Process With IRB Review Points 3 Months 1 Month 1 Month 2-3 Months 3 Months Interoperability Specifications, System Integ Preliminary Use Case Analysis Preliminary Project Plan RDSS Inspection Test/ Public Comment Interoperability Constructs Preliminary Use Case Final Use Case RDSS Comments Implementors/SDO Feedback 2-3 Months Maintenance Panel Approval, Public Release Resolve and Disposition Comments Legend Perspective TC color Domain TC color IRB

More Related