Architecture & Standards

The following is a list of some of the major collaborative organizations, projects, and activities focused in varying degrees
on 'Open' Health Information Technology (HIT) Architecture & Standards. 
**  Google search on links to Health Informatics Standards

*** See links to articles on Open Source Policy at Open Health News

YouTube Health Data Standards Video

Articles, reports, and papers by the Webmaster and others on collaborative, 'open source' health IT architecture and standards
* Visit Open Health News for more information about open health architecture & standards.

IT Architecture Defined

IT Architecture provides a blueprint to guide how an organization’s information technology (IT) and information management (IM) elements should work together to efficiently accomplish the mission of the organization. The IT Architectural blueprint describes a logical architecture for the organization and encompasses the following areas:  Business Architecture (BA), Information Architecture (IA), and Technical Architecture (TA).  The IT Architectural process is used to examine business priorities, plan future improvements, and acquire needed technology and applications.

* The webmaster has assumed that individuals visiting this site already have an extensive knowledge and interest in open source and health information technology (HIT).

If you would like to suggest new material or links to be added to this
web site, please email

Open IT Standards

The Open Source Institute has defined an Open Standard Requirement (OSR) that states the essential criteria of an Open Standard for the purposes of Open Source software development.

 - No Secrets: The standard must include all details necessary for interoperable implementation.
 - Availability: The standard must be freely and publicly available (e.g., from a stable web site) under royalty-free terms.
 - Patents: All patents essential to implementation of the standard must:
       - be licensed under royalty-free terms for unrestricted use, or
       - be covered by a promise of non-assertion when practiced by open source software
 - No Agreements: There must not be any requirement for execution of a license agreement, NDA, grant, click-through, or any other form of paperwork, to deploy conforming implementations of the standard.
 - No OSR-Incompatible Dependencies: Implementation of the standard must not require any other technology that fails to meet the criteria of this Requirement.