CCTOS: Overview of Software Components at 4 levels

Version 4.2, 12 Aug 2011, Etienne Saliez.

Introduction
( A ) Common Requirements

- Introduction:
- Framework:
- Item root class:
- Agents:
- Patient:
- Patient group:
- Care Provider:
- Group of Agents:

Care Team:

Group of agents in charge of a common patient.

Medical Patient Data, "Pitem":

Generic properties of information contained in the patient record.

Views:

Presentation issue about how to present patient data.

Observations:

The facts having been observed.

Health Issues, "problem":

Assesments about the observed fact, identified issues.

Activities:

In function of the current health issues, activities are initiated and need to be managed. Activities may be intended for diagnostic as well therapeutic purposes.

Communications and Notifications:

Although most of the time the user are connected on-line, message exchanges remain necessary.

Synchronization procedures:

Synchronization between the databases of network nodes.

Knowledge interface:

Standardization of interfaces to diverses types of knowledge.

A few more classes will probably be necessary:

This overview of modules is just a short introduction to an integrated way of thinking and more classes will probably be necessary as concept of common interest.

...

( B ) Additional Requirements

Introduction:

The patient may need to go to several care environments. The following sub Cardiologychapters look at specific implementations of the concept of collaborative work in healthcare.
Most aspects of the generic modules from the common trunk defined in chapter ( A ) can be reused, but additional aspects may be necessary in function of the following situations.

B.1 In function of professional profiles

B.2 In function of specific diseases:

Malaria:
HIV:
Cancer:
Cardio-vascular:
....

( C ) Adaptations in function of cultural differences and national legal requirements

Adaptations in function of cultural differences:

Spoken language,
Organization of medical centers
Level of available resources
....

Insurances:

Generic principles are similar, but many rules and exception depending of the country. Item of services may be well or not included in "all-in" packages of covered services. The approaches should be based on a generic tarification engine steered by tables containing the local prices and exeptions rules.

.......

D ) Freedom for exceptions and arbitratry local requirements

Arbitrary local choices must always remain possible, in case for any reason, the "common proposals" do not fit in a local situation. However this software is then developed on own resources.
For continuity reasons many existing local developements need to be maintained, but on long term the goal is to achieve convergences whenever possible.
The freedom for innovation is important:

Freedom for independent experimental work, not having to wait for formal approval by anyone else. However partners should always remain informed of new initiatives.
In general this is expected to focus on only a few specialized components at a time, in the scope of a modular architecture.
As far as the first steps appear to be of general interest, the community should integrate the new modules and contribute to further developments.