This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Architecture Board"

From HL7Wiki
Jump to navigation Jump to search
Line 56: Line 56:
 
*Projects
 
*Projects
 
**[[Substantivity project| HL7 Substantive change and documentation]]
 
**[[Substantivity project| HL7 Substantive change and documentation]]
**[[Canonical Clinical Ontology | Canonical Clinical Ontology ]]
 
 
**[[HL7 Document Location | HL7 Document Location]]
 
**[[HL7 Document Location | HL7 Document Location]]
**[[computable semantic links from FHIR |Development of computable semantic links from FHIR specs to RIM]]
 
 
**[[HL7 Business Architecture|BAM]]
 
**[[HL7 Business Architecture|BAM]]
 
*[[Arb_meeting_schedule | Meeting Schedule and Minutes]]
 
*[[Arb_meeting_schedule | Meeting Schedule and Minutes]]
Line 65: Line 63:
 
***[http://tscwiki.hl7.org/wiki TSC wiki ]
 
***[http://tscwiki.hl7.org/wiki TSC wiki ]
 
**Terms of Reference(TBD)
 
**Terms of Reference(TBD)
 
+
*Efforts we have sunset:
 +
**[[Canonical Clinical Ontology | Canonical Clinical Ontology ]]
 +
**[[computable semantic links from FHIR |Development of computable semantic links from FHIR specs to RIM]]
 
[[Category:ARB_work_in_progress]]
 
[[Category:ARB_work_in_progress]]
  

Revision as of 21:33, 30 August 2016

The Architecture Board is responsible for the architecture of the HL7 Standards.

ArB Mission

The HL7 ArB seeks to define a coherent architecture for HL7 work that defines the relationships among the HL7 work products and how they relate to other standards and components of local implementations. This architecture includes the Business Architecture by which these work products are produced and managed through their life cycle, the governance that will be enacted on these work products, and the scope of the standardization effort itself.

ArB Scope

The scope of the ArB's work covers:

  • Defining a coherent standards architecture for HL7 to strive towards.
  • Working within the organization to market and refine the architecture
  • Ongoing interaction with HL7 customers to market and refine the architecture
  • Consideration of the suitability of the organisational structures to deliver the architecture
  • Defining the procedures and compliance criteria that ensure the HL7 work products conform to the architecture to enable the achievement stated levels of interoperability
  • Tracks developments in underlying SDO's and standards and keeps HL7 appropriately informed

Membership

MemberAffiliationMemberAffiliation
Julian, Tony Co-ChairMayo ClinicConstable, Lorraine Co-ChairConstable Consulting Inc.
Kubick, Wayne Health Level Seven, Inc.
Bond,Andy NEHTA Loyd, PatrickICode Solutions
Dagnall, BoHP Enterprise Services Lynch, CecilAccenture
Hufnagel, Steve U.S. Department of Defense, Military Health System Milosevic, ZoranDeontik Pty Ltd
Hyland, MarioAEGIS.net, Inc Stechshin, Andy CANA Software and Service Ltd
Knapp, PaulKnapp Consulting 

Acknowledgements

The ArB extends a "Thank you" to
Jane Curry,  Grahame Grieve, Charlie Mead, John Koisch, Ron Parker   and AbdulMalik Shakir
for all of the work they have done to progress the work of the ArB.

Current Activities




  • All previous minutes are available by date via the Arb_minutes

ArB Communication Venues

The many venues ArB uses for communication are found at Communications.