Difference between revisions of "Talk:20110515 arb WGM Orlando Minutes"
m |
m (→Comments about Mission: new section) |
||
| Line 1: | Line 1: | ||
Charlie Mead: The proposed new mission statement is: | Charlie Mead: The proposed new mission statement is: | ||
The HL7 Architecture Board (ArB) is tasked by the HL7 Chief Technology Officer (CTO) and Technical Steering Committee (TSC) to define the HL7 Enterprise Architecture Specification (EAS). The EAS – when complete – will include an integrated a specification of the HL7 Business (organization) Architecture, as well as its corresponding Technology (specification) Architecture. The EAS thus includes definitions of the various HL7 work products; infrastructure (technical) and organizational (business) structures; relationships between work products, infrastructure and organization components; and governance requirements for the management of the various technical work products produced by HL7. In particular, the EAS is expected to provide HL7 members the details necessary to develop EAS-compliant specifications (including an organization-wide, EAS-compliant Implementation Guide), as well as provide HL7 external stakeholders – including implementers, vendors, and other standards-development organizations – relevant information about the various EAS components and relationships. | The HL7 Architecture Board (ArB) is tasked by the HL7 Chief Technology Officer (CTO) and Technical Steering Committee (TSC) to define the HL7 Enterprise Architecture Specification (EAS). The EAS – when complete – will include an integrated a specification of the HL7 Business (organization) Architecture, as well as its corresponding Technology (specification) Architecture. The EAS thus includes definitions of the various HL7 work products; infrastructure (technical) and organizational (business) structures; relationships between work products, infrastructure and organization components; and governance requirements for the management of the various technical work products produced by HL7. In particular, the EAS is expected to provide HL7 members the details necessary to develop EAS-compliant specifications (including an organization-wide, EAS-compliant Implementation Guide), as well as provide HL7 external stakeholders – including implementers, vendors, and other standards-development organizations – relevant information about the various EAS components and relationships. | ||
| + | |||
| + | == Comments about Mission == | ||
| + | |||
| + | Please add your comments in this section. | ||
Revision as of 18:35, 14 May 2011
Charlie Mead: The proposed new mission statement is: The HL7 Architecture Board (ArB) is tasked by the HL7 Chief Technology Officer (CTO) and Technical Steering Committee (TSC) to define the HL7 Enterprise Architecture Specification (EAS). The EAS – when complete – will include an integrated a specification of the HL7 Business (organization) Architecture, as well as its corresponding Technology (specification) Architecture. The EAS thus includes definitions of the various HL7 work products; infrastructure (technical) and organizational (business) structures; relationships between work products, infrastructure and organization components; and governance requirements for the management of the various technical work products produced by HL7. In particular, the EAS is expected to provide HL7 members the details necessary to develop EAS-compliant specifications (including an organization-wide, EAS-compliant Implementation Guide), as well as provide HL7 external stakeholders – including implementers, vendors, and other standards-development organizations – relevant information about the various EAS components and relationships.
Comments about Mission
Please add your comments in this section.
