This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Services Aware Enterprise Architecture Framework"
Jump to navigation
Jump to search
m |
|||
(2 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
+ | {{arb deprecated item}} | ||
+ | [[Category:Arb_Deprecated_item]] | ||
'''Services Aware Enterprise Architecture Framework (SAEAF)''' | '''Services Aware Enterprise Architecture Framework (SAEAF)''' | ||
Line 6: | Line 8: | ||
## Value Propositions | ## Value Propositions | ||
### Notion of Conformance | ### Notion of Conformance | ||
− | ### ( | + | ### Notion of Governance |
+ | ### Implementable Standards | ||
+ | ### Computable Semantic Interoperability | ||
+ | ### Specification Framework that contextualizes the "...ilities" (scalability, etc.) | ||
## Assumptions | ## Assumptions | ||
### Existing HL7 artifacts | ### Existing HL7 artifacts | ||
Line 19: | Line 24: | ||
### Assertions | ### Assertions | ||
## Artifacts | ## Artifacts | ||
+ | ## Tying back to the Value Propositions | ||
+ | ### Notion of Conformance | ||
+ | ### Notion of Governance | ||
+ | ### Implementable Standards | ||
+ | ### Computable Semantic Interoperability | ||
+ | ### Specification Framework that contextualizes the "...ilities" (scalability, etc.) | ||
# Implications | # Implications | ||
## Implications to existing interoperability paradigms (V2, V3, CDA, etc.) | ## Implications to existing interoperability paradigms (V2, V3, CDA, etc.) | ||
## Implications for the use/interpretation of the RIM | ## Implications for the use/interpretation of the RIM | ||
− | ## SDO's, with special emphasis towards OMG | + | ## [[saeaf_sdo|SDO's, with special emphasis towards OMG]] |
## Working groups, with special emphasis on SOA WG, MnM, INM, CDS, EHR, and Foundations SD | ## Working groups, with special emphasis on SOA WG, MnM, INM, CDS, EHR, and Foundations SD | ||
## JIC | ## JIC | ||
Line 78: | Line 89: | ||
#[[SAEAFSOAArtifacts|Artifacts for SOA]] | #[[SAEAFSOAArtifacts|Artifacts for SOA]] | ||
''For report to TSC only - - [[SAEAFBallot Quality|Ballot Quality]]'' | ''For report to TSC only - - [[SAEAFBallot Quality|Ballot Quality]]'' | ||
− | |||
− | |||
[[User:Ajulian|Tony]] 14:00, 7 August 2008 (UTC) | [[User:Ajulian|Tony]] 14:00, 7 August 2008 (UTC) |
Latest revision as of 19:04, 22 March 2010
Services Aware Enterprise Architecture Framework (SAEAF)
- Introduction and Background
- Context -- internal and external (business) drivers
- Value Propositions
- Notion of Conformance
- Notion of Governance
- Implementable Standards
- Computable Semantic Interoperability
- Specification Framework that contextualizes the "...ilities" (scalability, etc.)
- Assumptions
- Existing HL7 artifacts
- Message Payload Content
- Non-Payload Message Content
- Other (CDA, Vocabulary, CCOW, Datatypes, EHR-S FM, GELLO, PHR, etc.)
- Non-HL7 Input (sources, links, etc)
- [Listed In Moinutes]
- Existing HL7 artifacts
- Interoperability Service Contract Specifications
- RM-ODP Framework
- Viewpoints
- Assertions
- Artifacts
- Tying back to the Value Propositions
- Notion of Conformance
- Notion of Governance
- Implementable Standards
- Computable Semantic Interoperability
- Specification Framework that contextualizes the "...ilities" (scalability, etc.)
- RM-ODP Framework
- Implications
- Implications to existing interoperability paradigms (V2, V3, CDA, etc.)
- Implications for the use/interpretation of the RIM
- SDO's, with special emphasis towards OMG
- Working groups, with special emphasis on SOA WG, MnM, INM, CDS, EHR, and Foundations SD
- JIC
- NIST
- Tooling
- Potential Next Steps
- Developmental Governance (eg, ArB's role)
- Organizational Governance (eg, TSC's role)
- Appendices
- Conformance and Compliance Framework
- Dyanmic Framework
- Meta-Model for Services / UML Profile
- Service Principles
- Service Taxonomy
- 2bBAM
- Drivers(Goals, customer needs, Performance measurements) Tony - Review
- Organization(participants and roles) Tony - Review
- OrganizationStructures Tony- Review
- Organization Processes Tony - Review
- Artifacts Jane
- Taxonomy and roadmap of the standards John - Review
- Levels of Interoperability Service Contract Specifications(ISCS) (formerly known as trading partner agreements(TPA))
- Stack of specifications that support ISCS's John - Review
- Structure of HL7 delivers support for customers to craft ISCS
- Interoperability Service Specification
- Interoperability service contract specifications John - Review (Conformance and Compliance document from NCI as content)
- Meta-model
- Taxonomy of Services John - Review
- Service PrinciplesJohn - Review
- Conformance
- Conformance Criteria (assertions)
- Conformance adherence (Realization)
- Conformance Validation (Inspection/testing)
- Artifacts for SOA
For report to TSC only - - Ballot Quality
Tony 14:00, 7 August 2008 (UTC)