saif and sound: fast track to standard development
DESCRIPTION
SAIF and Sound: Fast Track to Standard Development. Leveraging rigorous process to accelerate standard development and approval through predictable and repeatable processes (Draft Proposal). SAIF adoption raises challenges Change management Cultural changes - PowerPoint PPT PresentationTRANSCRIPT
SAIF and Sound: SAIF and Sound: Fast Track to Standard Fast Track to Standard
DevelopmentDevelopment
Leveraging rigorous process to accelerate standard development and approval through predictable and repeatable processes
(Draft Proposal)
1
IssuesIssues
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 fragmentedhttp://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
OpportunityOpportunity
Leverage HL7 expertise to migrate to SAIF◦ Evolution rather than revolution◦ Project management◦ Domain analysis◦ V3 Design◦ Well-defined ballot process (GOM)
Stage the SAIF models into iterative milestonesLeveraging 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
GlossaryGlossary
HDF◦ HL7 Development Framework
DAM◦ Domain Analysis Model
DIM◦ Design Information Model◦ D-MIM and R-MIM are equivalent
for message designsITS
◦ Implementation Technology Specification
GOM◦ HL7 Governance and
Operations ManualPLCPD
◦ Project Life Cycle for Product Development
SAIF◦ Services Aware
Interoperability Framework
CIM◦ Computation-
Independent Model◦ SAIF Conceptual Model
PIM◦ Platform-Independent
ModelPSM
◦ Platform-Specific ModelSOA
◦ Service Oriented Architecture
4
Model Driven DevelopmentModel Driven Development5
OMG – Object Management Group OMG Model Driven Architecture
www.jot.fm/issues/issue_2006_03/column4/
An example of Model Driven Architecture: Software Development
Model/Artifact
Role
The ECCF Specification The ECCF Specification Stack 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, Procedures Localized Information Model,
Transforms, Schema
Collaboration scripts, Orchestrations,
Realized Interfaces
Execution Context, Platform Bindings, Deployment Model
Critical to interoperability standards
Reference Model of Open Distributed Processing (RM-ODP)
RM-ODP
7
act 1.3.1: Project Life Cycle for Product Development
HL7 Protocol Specifications
(.1) Request to enhance or create a new product
(.2)
Request to sunset product (.23)
Requestapproved
(.24)
Sunset Product
(.25)Project sunset
Project Initiation/Approval (.5)
ApprovalReceived
(.6)
Cancel or Withdraw (.4)
Analysis (.7)
Design (.8)
QVSD
QVSD
(.10) SeekComments
Draft Specification (.9)
QVSD
(.11) Comments-Only
Ballot
Ballot type(.12)
DSTU(.13)
DSTU Ballot (.14)
QSVD
Finalize Specification (.17)
Specification and Training
(.15)
QVSDIndustry Use
(.16)
Informative Ballot (.21) QVSD
Normativeor
Informative(.22)
QVSD
Normative Ballot (.18)
Pass(.19) Publication (.20)
QVSD
Project Initiation
Analysis
Design
Ballot
Project Sunset
HL7 Protocol Specification
Legend
HL7 Protocol Specification
Completed
failed
no
yes
yes
no
yes
yes
no
passed
review
no
normative
informative
normative
Domain Analysis
Design
Implementation
Conceptual Model
Platform Independent
Model
Platform Specific Model
HDFPLCPD SAIF
Analysis
Design
ITS
DIM
Ballot
DAM
Ch
oic
e
Draft
NormativeProject 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
Domain Analysis
Design
Conceptual Model
Platform Independent
Model
Platform Specific Model
HDFPLCPD SAIF
Analysis
Design
ITS
DIM
Ballot
DAM
Ch
oic
e
Project ManagementProject Management MethodologyMethodology ArchitectureArchitecture
Implementation
ProcessMilestones Artifact Specification
9
Domain Analysis
Design
Conceptual Model
Platform Independent
Model
Platform Specific Model
HDFPLCPD SAIF
Analysis
Design
PSM
PIM
Ballot
CIM/Conceptual
Ch
oic
e
SAIF AdoptionSAIF Adoption
Implementation
DAM CIMDIM PIMITS PSM
SAIF AdoptionSAIF 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
AnalysisMilestone
Domain Analysis Design
Reconcile Analysis
DesignMilestone
PIM
Ballot
ConceptualI2
I1
Ballot
ConceptualI1
PSM
PIM
Ballot
ConceptualI2
I2
DSTU1
Reconcile Design
ImplementationSpecification
DraftMilestone
Trial
January May SeptemberSeptember
RIM or Vocabulary Harmonization
12
NormativeMilestone
Reconcile
PublicationMilestone
PSM
PIM
Normative Edition
ConceptualI2
I1
Training
DSTU issues collected
PSM
Ballot
N1 N1
13
SeptemberMayJanuary
April July August November
RIM Enhancementsfor next year
RIM and Vocabulary Harmonization Cycles
HL7 Normative Ballot
September
New content
Harmonization + RIM Balloting
Harmonization Needs Harmonization Needs 14
Harmonization Need
RIM Change Proposal
VocabularyChangeProposal
Leads to RIM revision (Normative ballot)
Used to update the Vocabulary reference
HL7 Normative Ballot
15
September
MayJanuary
RIM Change Proposal Collection
HL7 Normative Ballot
September
APPROVAL @September WGM
Technical Reviews replace
Harmonization meetings
Frequency: three times per year
DraftRIM Change ControlProcess
Technical review
Publish RIM Changes
for next year
Harmonization HarmonizationHarmonization
Work Group Approval Work Group Approval
Technical review
Work Group Approval Work Group Approval
Technical review
Work Group Approval Work Group Approval
Improve visibility for pending Normative RIM
16
SeptemberMayJanuary
Vocabulary Change Proposal Collection
September
Technical Reviews precede
Harmonization meetings
Frequency: three times per year
DraftVocabulary Change Control Process
Harmonization Harmonization Harmonization
Publish approved changes
Publish approved changes
Publish approved changes
Projects apply changes
Projects apply changes
Projects apply changes
Projects apply changes
Projects apply changes
Projects apply changes
Improve visibility for pending vocabulary
enhancements
Technical review
Work Group Approval Work Group Approval
Technical review
Work Group Approval Work Group Approval
Technical review
Work Group Approval Work Group Approval
Sponsor: Sponsor: Project Services Work Group (PSWG)Project Services Work Group (PSWG)Please direct comments to: Please direct comments to: [email protected] [email protected] If you are not subscribed to the PSWG list, contact Co-chairsIf you are not subscribed to the PSWG list, contact Co-chairs Rick Haddorff ( Rick Haddorff ([email protected]@mayo.edu)) or Freida Hall (or Freida Hall ([email protected]@va.gov))
Questions/Comments?