20080821 ARB Jump Start

From HL7Wiki
Jump to navigation Jump to search

Architecture Board

20080819 August out-of-cycle Day 3


Thursday Morning 0800 - 1130

Attendance

?? Depicts those expected who have not appeared.

NameRoleAffiliationemail
Curry, Jane ArB Health Information Strategiesjanecurry@healthinfostrategies.com
Julian, Tony ArB Mayo Clinicajulian@mayo.edu
Koisch, John ArB NCIkoisch_john@bah.com
Larsen, Ed Guest HITSPerlarsen@ix.netcom.com
Lynch, Cecil ArB ontoreason LLCclynch@ontoreason.com
Mead, Charlie?? ArB Booz Allen Hamiltoncharlie.mead@booz.com
Orvis, Nancy ?? ArBDODnancy.orvis@tma.osd.mil
Parker, Ron ArB CA Infowayrparker@eastlink.ca
Quinn, John ArBHealth Level Seven, Inc.jquinn@HL7.org
Shakir, Abdul-Malik ArB Shakir ConsultingShakirConsulting@cs.com
Wrightson, Ann Guest NHS(IHC)ann.wrightson@wales.nhs.uk
Yongjian, Bao ArB GE Healthcareyongjian.bao@med.ge.com

Relationships between HL7 and other Organizations that needs to be revisited or added (30 minutes)

Discussion Defered

Conformance at the Blueprint Level

Refer to for model mapping terms to RM-ODP viewpoints

Notes to Reader: The elipses <...> is intended to be filled in upon instantiation of the profile. 
<modal verb> refers to the ANSI-speak modal verbs SHALL, SHOULD, MAY.
A service in this context is an abstract concept with no technology or platform binding.
A conformance assertion provides a checklist to test conformance of a given profile at a given level.
  • Business context
    • Definition:
      • scope
      • vision
      • requirements
      • use cases
      • ties to EHR-S Functional Profile.
    • The user expectations are
      • Roles
      • relationships
      • Policies
      • clouds
      • EHR-S FP
      • Use Cases
    • Business context Conformance Assertions:
      • Specification is of interest to <...>
        • that will take on the roles<...>
        • and exhibit relationships <...>
        • and exhibit <...>Behaviours
      • Specification has traceability to <...>HL7 Reference Material (EHR-S FM, RIM, ETC)
        • Explanation
        • Traceability
      • Accountability
        • This specification service owner is <...> and the
        • information owner is <...>
  • Blueprint/Architectural Profiles
    • Composition
      • Information component
      • Computational set of components
        • Groups of operations focused by usage(outlooking)
    • Service Profile Conformance Assertions
      • Capabilities will be exhibited that are supported by <...> views and operations that align with usage as outlined in the Business Context.
      • Special features of this view are <...>
      • Optionally
        • The information view <modal verb> be decoupled from the computational profile
        • This service profile is designed to support <...> class of information views.
        • Implementation patterns <modal verb> be Guided/influenced by policy
        • This service profile is designed to support the implementation of <...> policies.
  • Domain Information Model (DIM)
    • Definition:
      • Domain Information Model is <...>
    • Assertions
      • DIM has traceability to <...> HL7 Reference Material (EHR-S FM, RIM, ETC)
      • Optionally may tie to
  • Dynamic Blueprint??Better Word??
    • Definition
      • Functional decomposition
      • Use case realization
      • Application
      • Collaborations
    • Assertions
      • Application roles are <...>
      • Initiated by <...>
      • Optionally followed by <...>

Conformance at the Platform Independent level

  • Business Governance
    • Consists of
      • Rules
      • focus
      • Purpose
      • Policies
      • User roles
      • Timing
      • Sequencing(Potential)
      • Relationships
      • Technical design decisions that presume policy/Policies
    • Assertions
      • Set(s) of implications, consequences
      • Note to consumers EDITOR fill this out!
      • V3 core principles
  • CIM, LIM
    • Definitions
    • Assertions
      • The artifacts are assertions of conformance.
      • Optionally include extra assertions that reflect quality/functional requirements associated with the invormation views.
  • Interface Specifications
    • Definition
    • Assertions
      • The artifacts are assertions of conformance.
      • Optionally include extra assertions that reflect quality/functional requirements associated with the invormation views.
  • Dynamic Model
    • Definition
    • Assertions
      • The
        • timing,
        • sequencing,
        • shared state,
        • rules
      • are realized by
        • roles,
        • relationships,
        • interactions,
        • exchanges,
        • channels.
      • Optionally include extra assertions that reflect quality/functional requirements associated with the invormation views.


NOTE: Designers in healthcare have a certain mental defect that empowers them to perform their function to the chagrin of those not so empowered.


Note RE a person object with dob and name.  
Programmer makes dob and name private, then creates setters and getters, wherein are defined the business rules.
When you bury the rules in the setters and getters you are hiding the behaviours.  Assuming a function CheckContent, the rules are hidden in the function.  
The behaviour needs to be explicit at the process level.  
Objects have encapsulation, services have virtualization:  Technically you are not doing any different between service and objects (except polymorphism, recursion).

Conformance at the Platform Binding Level

Assertions are the artifacts themselves: Optionally include extra assertions that reflect quality/functional requirements associated with the invormation views.

Dynamic Model

Discussion was held about the dynamic model. AMS captured the changes discussed in the model as expressed in EA(see diagram).

Screen of the EA

Example of using the taxonomy:

Taxonomy-instantiation.JPG

Glide Path (75 Minutes)

  • Assignments, Ownerships
  • Review Schedule
    • September 11th is drop dead date for readiness for the meeting; final review

Thursday 1300 + (Optional)

TBD  Tony Julian