With respect to the term "Life Cycle Model" we must remember that we
are
speaking of the representation of the processes and activities that
will
lead, over the lifetime of the envisioned system, to the trajectory
of
system configurations. There will be the general form of processes
and
activities applicable to the general model, like "Rapid Prototyping"
(e.
g. as depicted in ASTM E-1340) to which will be added specific
details
related to the specific system and enterprise being considered. The
generalities for a system in the health information domain will have
concepts and functions that cross numerous specific enterprises and
specialty disciplines which will then be conditionmed by the detail
applicable to the individual enterprise. Much of this conceptual
detail
can be reflected in the conceptual content standards and referenced
in
the Life Cycle Model documentation (e.g. IEEE 1362, 830, 1058) that
are
associated with the Zachman Framework concepts applied to the system
of
interest. For VistA, a general template document triad can be
prepared
that can be then tailored for the specific system and project of
interest
to a given health information architecture. In working with the
health
professional specialty disciplines, the "information system
engineers"
involved have the ability to convey to these specialties the
magnitude of
the effort involved (which may include "business process
re-engineering")
that is frequently not even comprehended; many may think the effort
is the
same as buying a computer box of the shelf from the local electronic
store. So the recognition of the Life Cycle Model and its
implications is
critical and something both the Infoirmation systems folks and the
health
specialty disciplines both need to know with lots of common ground.
RP LCM
is most useful to (but not unique to) healthcare because of the rapid
evolution of the underlying knowledge (e. g. Genomics, Proteomics,
Metabolomics), terms VistA is still trying to cath up with. For VistA
education in the "Common Ground" is key to how benefiiciary Acquirers
will
be able to work synergistically with the Suppliers who will enable
them
make it all work. Thus WorldVistA must have closely communicating
Project
teams and Educational Programs that will set the stage for what the
Supplier organizations (e.g. VSA) will do so that these organizations
can
realize their essential contribution to the System Life Cycle.
I hope that this wasnt too long.
On Wed, 29 Jun 2005, Gregory Woodhouse wrote:
I assume that by "ACT" you mean "activity"? This is interesting
because it's
a case in which I find my instinct and intuition at odds. My basic
instinct
as a developer is to break it up into a (possibly cyclic) sequence
of
(timed?) events. My intuition, on the other hand, is that on the
semantic (or
even ontological) level, it's a basic concept, and how I might
implement an
activity in a real system actual reflects my knowledge about
activities.
The Key is joint work of information systems engineers (ISE) with the
health
specialty disciplines (HSD)throughout the System Life Cycle (SLC).
And I have to ask: How do you see Deming's ideas being applied to
medicine?
Deming's ideas affect both the conceptual content (HSD) and the
implemented content (ISE) that result in an effective system behavior
that
positively supports the measured outcome of the healthcare
enterprise.
Health service professional disciplines will be involved in the
measurement process. Thes esteps are all part of the healthcare
"business
process".
===
Gregory Woodhouse
[EMAIL PROTECTED]
"The policy of being too cautious is
the greatest risk of all."
--Jawaharlal Nehru
On Jun 28, 2005, at 6:37 PM, Thurman Pedigo wrote:
I have been watching this thread with a bit of nagging abstraction
- then
recognized it. Presented is a modified technique of W. Edwards
Deming - the
guy who taught the Japanese how to eat Detroit's lunch (in the
50's).
Shewhart was the originater in the 20's. A brief link:
http://www.balancedscorecard.org/bkgd/pdca.html
PLAN; DO; CHECK; ACT
And broken down:
PLAN:
1. requirements analysis
2. design
DO:
3. coding
4. documentation
CHECK:
5. testing
ACT:
6. maintenance
And the cycle restarts.
(Of course, this list could be elaborated/expanded.)
Perhaps the post industrial era adds new challenges. However, the
basic
concept of simplification and persistance have merits not met by
the "throw
this away and build anew" philosophy that seems to invade our
work.
Unfortunately, we failed to appropriately integrate Deming with
medicine.
thurman
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration
Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast.
http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration
Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
