Presentation is loading. Please wait.

Presentation is loading. Please wait.

One-release-per-year One-approval-per-year One-standard-per-year Leveraging rigorous process to accelerate standard development and approval through predictable.

Similar presentations


Presentation on theme: "One-release-per-year One-approval-per-year One-standard-per-year Leveraging rigorous process to accelerate standard development and approval through predictable."— Presentation transcript:

1 One-release-per-year One-approval-per-year One-standard-per-year Leveraging rigorous process to accelerate standard development and approval through predictable and repeatable processes (Draft Proposal) 1

2 Issues SAIF adoption raises challenges ◦Change management ◦Cultural changes ◦Migration of existing artifacts Voluntary HDF adoption has not worked ◦“Analysis is a waste of time let’s skip it” HL7 V3 change request process is fragmented http://www.hl7.org/memonly/dbtracker_V3/index.cfm Work groups use internal spreadsheet to track change requests ◦The ballot is sometimes the de-facto change submission process ◦The RIM and Vocabulary rely on harmonization: ◦Structured Documents is using wiki to collect CDA R3 change requests Veteran HL7 developers have expressed concern that introducing new processes and introduction of project management will slow down development of standard 2

3 Opportunity Leverage HL7 expertise to migrate to SAIF ◦Evolution rather than revolution ◦Project management ◦Domain analysis ◦V3 Design ◦Well-defined ballot process (GOM) Scheduling model development using iterative milestones Leveraging project management Leverage informative and “for comment” ballots to validate scope and requirements ◦Ballot Conceptual/Domain Analysis Models ◦Stage ballots for optimal engagement with HL7 members and stakeholders 3

4 Glossary HDF ◦HL7 Development Framework DAM ◦Domain Analysis Model ◦D-MIM DIM ◦Design Information Model ◦R-MIM ITS ◦Implementation Technology Specification SAIF ◦Services Aware Interoperability Framework CIM ◦Computation- Independent Model ◦SAIF Conceptual Model PIM ◦Platform-Independent Model PSM ◦Platform-Specific Model 4

5 Model Driven Development 5 OMG – Object Management GroupOMG Model Driven Architecture www.jot.fm/issues/issue_2006_03/column4/ An example of Model Driven Architecture: Software Development Model/Artifact Role

6 The ECCF Specification Stack Topic Specification Enterprise / Business Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Conceptual Model (HDF DAM) Domain Analysis (Business) Model Domain Analysis (Information) Model Domain Analysis (System Interactions) Existing Platform capabilities Platform- Independent Model (HL7 Std Design) Business Governance Design Information Model, Constrained Information Model, Localized Information Model, Hierarchical Message Definition Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Existing Platform models, libraries, etc. Platform- Specific Model (ITS) Rules, ProceduresLocalized Information Model, Transforms, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context, Platform Bindings, Deployment Model Critical to interoperability stds. Reference Model of Open Distributed Processing (RM-ODP) RM-ODP

7 7 Domain Analysis Design Implem entation Conceptual Model Platform Independent Model Platform Specific Model HDFPLCPDSAIF Analysis Design ITS DIM Ballot DAM Choice Draft Normative Project Life Cycle for Product Development (PLCPD) HL7 Development Framework (HDF) Services Aware Interoperability Framework (SAIF) Domain Analysis Model Design Info Model Implementation Technology Spec.

8 8 Domain Analysis Design Conceptual Model Platform Independent Model Platform Specific Model HDFPLCPDSAIF Analysis Design ITS DIM Ballot DAM Choice Project Management MethodologyArchitecture Implem entation ProcessMilestones Artifact Specification

9 9 Domain Analysis Design Conceptual Model Platform Independent Model Platform Specific Model HDFPLCPDSAIF Analysis Design PSM PIM Ballot CIM/ Conceptual Choice SAIF Adoption Implem entation DAM  CIM DIM  PIM ITS  PSM

10 SAIF Adoption We need definitions of SAIF artifacts: ◦Required artifacts and models  Relevant view-points only ◦Optional artifacts and models  PSM?  Are they reusable? We need publication/ballotable examples of SAIF artifacts We need to revise the process definitions in the HDF and reference the new artifacts specified by SAIF 10

11 11 Analysis Milestone Domain AnalysisDesign Reconcile Analysis Design Milestone PIM Ballot Conceptual I2 I1 Ballot Conceptual I1 PSM PIM Ballot Conceptual I2 DSTU1 Reconcile Design Implementation Specification Draft Milestone Trial JanuaryMaySeptember RIM or Vocabulary Harmonization

12 12 Normative Milestone Reconcile Publication Milestone PSM PIM Normative Edition Conceptual I2 I1 Training DSTU issues collected PSM Ballot N1

13 13 SeptemberMayJanuary AprilJulyAugust November RIM Enhancements for next year RIM and Vocabulary Harmonization Cycles HL7 Normative Ballot September New content Harmonization + RIM Balloting

14 Harmonization Needs 14 Harmonization Need RIM Change Proposal Vocabulary Change Proposal Leads to RIM revision (Normative ballot) Used to update the Vocabulary reference

15 HL7 Normative Ballot 15 September MayJanuary RIM Change Proposal Collection HL7 Normative Ballot September APPROVAL @ September WGM Technical Reviews replace Harmonization meetings Frequency: once per quarter Draft RIM Change Control Process Draft RIM Change Control Process Work group technical review Publish RIM Changes for next year Harmonization

16 16 SeptemberMayJanuary Vocabulary Change Proposal Collection September Technical Reviews precede Harmonization meetings Frequency: once per quarter Work group technical review Draft Vocabulary Change Control Process Draft Vocabulary Change Control Process Harmonization Publish approved changes Projects apply changes

17 Sponsor: Project Services Work Group (PSWG) Please direct comments to: psc@lists.hl7.org If you are not subscribed to the PSWG list, contact Co-chairs Rick Haddorff (haddorff.richard@mayo.edu) or Freida Hall (freida.hall@va.gov) psc@lists.hl7.orghaddorff.richard@mayo.edufreida.hall@va.govpsc@lists.hl7.orghaddorff.richard@mayo.edufreida.hall@va.gov Questions/Comments?


Download ppt "One-release-per-year One-approval-per-year One-standard-per-year Leveraging rigorous process to accelerate standard development and approval through predictable."

Similar presentations


Ads by Google