Skip to content

The Teksouth Intelligent Healthcare Practice

  • narrow screen resolution
  • wide screen resolution
  • Increase font size
  • Decrease font size
  • Default font size
The Intelligent Healthcare Architecture PDF Print E-mail

Enterprise Architecture is our 2nd solutions focus area for the Intelligent Healthcare Practice.

We generally begin all of our solution engagements with an enterprise architecture  assessment along with a strategic review. To aid in making that process more agile we've developed a core solution architecture that links to all of our primary solution design options. This preliminary or generic IH architecture is later tailored or mapped to each client's individual needs.

The core Intelligent Healthcare Enterprise Architecture is meant to provide a reference architecture at the ‘ecosystem’ level with specific drill down views of key elements within typical Healthcare IT environments. Enterprise Architecture is far too often conducted as an isolated or highly interpretative activity. There are a variety of architectures to keep in mind, including:

•    Framework Architectures (FEAF, DoDAF, Zachman)
•    Design Architectures (UML)
•    Reference Architectures (e.g. NHIN)
•    Infrastructure Architectures (NETOPs, Datacenter, Telecommunications)
•    Logical & Conceptual Architectures (for business process and data)
•    Services Oriented Architecture (SOA)

All of these types of architecture are valid in their own contexts, unfortunately though this proliferation of architectures often becomes an obstacle rather than an integration aid merely adding to an already complicated situation. The Intelligent Healthcare EA adheres to elements of DoDAF, FEAF and UML but can also be viewed separately from any specific EA framework – our goal is not to add to the current level of complexity but rather to illustrate core concepts using broadly accepted architecture techniques.

The Intelligent Healthcare technical reference architecture is more of a near-term exploration into how IH might be manifested in actual solution implementations.