Example Healthcare Zachman
Example Healthcare Zachman
Example Healthcare Zachman
When
(Time)
Scope
(Contextual)
1. Personal and
public health
impact, and care
delivery business
case.
2. Identification of
significant health
care and care
delivery events.
Enterprise and
Environment
(Conceptual)
8. Sequence and
timelines of health
care services.
Health Information
System (Logical
Design)
7. Personal health
benefit and care
delivery business
objectives.
13. System
functional
requirements.
Health Information
Technology
(Physical Design)
19. System
operational
requirements.
Health Information
Components
(Modules and
subsystems)
25. Technical
requirements.
Functioning Health
Information
System
31. Technology
operational
requirements.
Who
What
(People)
(Content)
Vision (Guidelines)
3. Essential
4. Description of
health service
important health
organizations and
service and care
their functions.
delivery
information.
Design (Standards)
9. Healthcare
10. Semantic
information
description of
system workflow.
health care
processes.
15. Health care
16. Logical data
information
model for health
system humancare information.
system interface
architecture.
Implementation (Standards)
21. Health care
22. Physical data
information
model for health
system humancare information.
system interface
description.
27. System
28. Health care
security
information
architecture and
metadata, and
operations.
DBMS scripts.
Operation (Standards)
33. IS participant
34. Functioning
description.
database,
knowledgebase.
How
(Function)
Where
(Network)
5. Important
health care and
care delivery
services.
6. Identification
and description of
organization and
individual
locations.
11. Conceptual
activity model of
health care
delivery.
17. Application
architecture with
function and user
views.
23. System
design, language
specification, and
structure charts.
29. Code
statements,
control blocks,
DBMS stored
procedures, etc.
35. User
procedural and
system
documentation.
36. Operating
health system
communication
network.
MCD 12/22/97
fn:HISB_ISA
Cell
Row
Column
1.
Scope
Why
2.
When
3.
Who
4.
What
5.
How
6.
Where
Why
7.
Enterprise &
Environment
8.
When
9.
Who
10.
What
MCD 12/22/97
fn:HISB_ISA
Row
Column
11.
How
12.
Where
Why
13.
Health Info
System
14.
When
15.
Who
16.
What
17.
How
18.
Where
19.
20.
Health Info
Technology
Why
When
MCD 12/22/97
fn:HISB_ISA
Who
22.
What
23.
How
24.
Where
25.
Health Info
Components
Why
26.
When
27.
Who
28.
What
29.
How
30.
Where
31.
32.
Functioning
Health Info
System
Why
When
MCD 12/22/97
fn:HISB_ISA
Who
What
35.
How
36.
Where
When filling out the chart consider that the framework is a continuum from theory to practice: healthcare informatics standards and
standardization activities as well as non-informatics activities may be relevant to all cells in this framework.
Standards developers and other organizations may identify a cell for a primary classification and possibly one or more other cells for
secondary classifications. For example:
ANSI X12N and Health Level Seven specifications would likely have a primary classification in Cell 30 as information
communication protocols.
ASTM E 622, 627, and 1340 would likely be relevant to Cell 13 while the Federal Information Processing Standard for
IDEF1X data modeling would most likely fit in Cells 16 and 22.
Organizations such as AHCPR and JCAHO could add practice, care delivery, and information standards to the framework.
While a proponent may enter a standard or activity in any number of cells in the framework, identification with a single cell indicates
that the standard or activity is highly focused and concentrated on a single important aspect of healthcare informatics.
Additional information on the Zachman Architecture can be found at http://www.zifa.com/, the home page for the Zachman
Institute.
Comments and suggestions should be sent to Mark Diehl at [email protected] or fax 301-816-8301.
MCD 12/22/97
fn:HISB_ISA