This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20080617 arbJumpStartMinutes"
Jump to navigation
Jump to search
m |
|||
(10 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | == | + | {{Arb_Old_Minutes}} |
− | + | '''Architecture Board''' | |
− | + | ||
− | + | Minutes of the 20080617 June out-of-cycle Day 2 | |
− | + | ||
− | + | ||
− | + | ==Attendance== | |
− | + | <table border="1"><tr><td>Name</td><td>Role</td><td>Affiliation</td><td>email</td></tr> | |
− | + | <tr><td>B</td><td>G</td><td>guest</td><td>?</td><td>?</td><tr> | |
− | + | <tr><td>Charlie, Mead </td><td> ArB </td><td>Booz Allen Hamilton</td><td>charlie.mead@booz.com</td></tr> | |
− | + | <tr><td>Curry, Jane </td><td> ArB </td><td>Health Information Strategies</td><td>janecurry@healthinfostrategies.com</td></tr> | |
− | + | <tr><td>Julian, Tony </td><td> ArB </td><td>Mayo Clinic</td><td>ajulian@mayo.edu</td></tr> | |
− | + | <tr><td>Koisch, John </td><td> ArB </td><td>Boz</td><td>koisch_john@bah.com</td></tr> | |
− | + | <tr><td>Larsen, Ed </td><td> guest </td><td>HITSP</td><td>erlarsen@erlinc.com</td></tr> | |
− | + | <tr><td>Mulrooney, Galen </td><td> guest </td><td>VHA</td><td>galen.mulrooney@med.va.gov</td></tr> | |
+ | <tr><td>Orvis, Nancy </td><td> ArB</td><td>DOD</td><td>nancy.orvis@tma.osd.mil</td></tr> | ||
+ | <tr><td>Quinn, John </td><td> ArB</td><td>Health Level Seven, Inc.</td><td>jquinn@HL7.org</td></tr> | ||
+ | <tr><td>Rogers, Rich </td><td> guest </td><td>IBM</td><td>rrogers@us.ibm.com</td></tr> | ||
+ | <tr><td>Robertson, Scott</td><td>guest</td><td>Kaiser Permanente</td><td>scott.robertson@kp.com</td></tr> | ||
+ | <tr><td>Shakir, Abdul-Malik </td><td> ArB </td><td>Shakir Consulting</td><td>ShakirConsulting@cs.com</td></tr> | ||
+ | </table> | ||
==Agenda== | ==Agenda== | ||
Line 47: | Line 53: | ||
*** AMS - This architecture is not a replacement for or an alternative to XXX - it encompasses, supports, and facilitates the stuff that we already have. The Health Domain Enterprise domain needs services in conjunction with the other components, and HL7 needs to take a leadership position. There is an aculturation issue. | *** AMS - This architecture is not a replacement for or an alternative to XXX - it encompasses, supports, and facilitates the stuff that we already have. The Health Domain Enterprise domain needs services in conjunction with the other components, and HL7 needs to take a leadership position. There is an aculturation issue. | ||
* Lunch | * Lunch | ||
− | * Conformance and Compliance | + | * Conformance and Compliance - A profile is a set of constrained assertions that force a yes | no answer to the question "are you compliant to ..." Conformance Assertions that are present in the services specs are equivalent to the conformance profile (HL7). Each viewpoint makes a set of assertions as part of its specifications. Conformance statements historically further constrain the conformance assrtions to demonstrate the degree of compliance of an implementation. |
{| border="1" | {| border="1" | ||
|+ Conformance Levels | |+ Conformance Levels | ||
|- | |- | ||
− | | | + | | colspan="6" align="center" | Assertions Per Viewpoint |
|- | |- | ||
− | + | ! - !! Business !! Information !! Computation !! Engineering !! Technology | |
|- | |- | ||
− | | Reference || / || / || / || / || / | + | | Reference || / || / || / || / || / |
|- | |- | ||
| Domain || + || + || + || - || / | | Domain || + || + || + || - || / | ||
Line 63: | Line 69: | ||
|- | |- | ||
| Implementation Spec || - || - || + || + || - | | Implementation Spec || - || - || + || + || - | ||
+ | |- | ||
+ | | colspan="6" align="center" | Key: +: Required -: Optional /: Not Allowed | ||
|} | |} | ||
* NO: DoD SOA Architecture | * NO: DoD SOA Architecture | ||
+ | [[Category:Arb Old Minutes]] [[User:ajulian|Tony Julian]] |
Latest revision as of 21:39, 19 March 2010
Architecture Board
Minutes of the 20080617 June out-of-cycle Day 2
Attendance
Name | Role | Affiliation | ||
B | G | guest | ? | ? |
Charlie, Mead | ArB | Booz Allen Hamilton | charlie.mead@booz.com | |
Curry, Jane | ArB | Health Information Strategies | janecurry@healthinfostrategies.com | |
Julian, Tony | ArB | Mayo Clinic | ajulian@mayo.edu | |
Koisch, John | ArB | Boz | koisch_john@bah.com | |
Larsen, Ed | guest | HITSP | erlarsen@erlinc.com | |
Mulrooney, Galen | guest | VHA | galen.mulrooney@med.va.gov | |
Orvis, Nancy | ArB | DOD | nancy.orvis@tma.osd.mil | |
Quinn, John | ArB | Health Level Seven, Inc. | jquinn@HL7.org | |
Rogers, Rich | guest | IBM | rrogers@us.ibm.com | |
Robertson, Scott | guest | Kaiser Permanente | scott.robertson@kp.com | |
Shakir, Abdul-Malik | ArB | Shakir Consulting | ShakirConsulting@cs.com |
Agenda
- 8-9 - review of OASIS, CBDI work
- 9-11 – tbBAM modeling
- 11-12 – open discussion with Observers
- 12-1 – lunch
- 1-2 – review of relevant NCI work
- 2-3 – review of relevant DoD work
- 3-4 – review of relevant Infoway work
- 4-5 – open discussion with Observers
Minutes
- Oasis Service Description Model
- NCI Service Taxonomy
- CBDI Taxonomy of Services
- Discussion of the HITSP / NHIN services, and the use cases for architecture itself. JC - the problem is not a system architecture, it is enterprise in scope and we need enterprise architecture. JK - discussed the NCI service taxonomy's assumption as a way to get buy in from organizations (using use cases, and describing dependencies for those use cases that are specified as services). EL - HITSP / NHIN really needs the architecture offerings from the HL7 ArB, including principles, taxonomy, service offerings, contract specifications.
- Principles
- Initial cut at principles:
- Virtualization
- Aggregation / Composition
- Unity of Purpose
- Technology Independence
- Service Specification should support a Layered Conformance Policy
- Each Service Specification (each service has many service specifications) must belong to a conformance layer. Each conformance layer must have rules associated with it.
- each service should also belong to the HL7 taxonomy
- use Should Shall May
- We should follow the Oasis Format (Statement, Rationale, Implications)
- Additional Principles (from other sources - Oasis)
- Separation of Concerns should be added
- Parsimony should be added to unity of purpose
- RR suggested looking at soaprinciples.com
- AMS - This architecture is not a replacement for or an alternative to XXX - it encompasses, supports, and facilitates the stuff that we already have. The Health Domain Enterprise domain needs services in conjunction with the other components, and HL7 needs to take a leadership position. There is an aculturation issue.
- Initial cut at principles:
- Lunch
- Conformance and Compliance - A profile is a set of constrained assertions that force a yes | no answer to the question "are you compliant to ..." Conformance Assertions that are present in the services specs are equivalent to the conformance profile (HL7). Each viewpoint makes a set of assertions as part of its specifications. Conformance statements historically further constrain the conformance assrtions to demonstrate the degree of compliance of an implementation.
Assertions Per Viewpoint | |||||
- | Business | Information | Computation | Engineering | Technology |
---|---|---|---|---|---|
Reference | / | / | / | / | / |
Domain | + | + | + | - | / |
Use Case | + | + | + | - | / |
Implementation Spec | - | - | + | + | - |
Key: +: Required -: Optional /: Not Allowed |
- NO: DoD SOA Architecture Tony Julian