CCTOS: Overview of Software Components at 4 levels

Version 22 Aug 2016, (initially 12 Aug 2011), Etienne Saliez /

( A ) Common Requirements:
- Introduction:
  - The first step is here to identify the most common requirements, regardless of any particular disease, nor medical specialties,nor cultural environment.
- Framework:
  - An overview of the framework on which the application will be build.
- Item root class:
  - The most generic common properties intended to be used in most subsequent application modules.
- Agents:
  - General properties of agents expected to participate in the network.
- Patient:
  - Patient identification and root of the patient record.
- Patient group:
  - A way to retrieve a group of patients having a common characteristic.
- Care Provider:
  - Generic properties of care providers.
- Group of Agents:
  - Agents representing a group of individual agents. For example a hospital.
- 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.
- Links:
  - Many links between Observations, Health Issues, Activities, as well links to medical knowledge. Links are autonomous objects with their own properties.
- 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.
- 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.

CCTOS: Overview of Software Components at 4 levels

( A ) Common Requirements:

( B ) Additional Requirements:

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

D ) Freedom for exceptions and arbitratry local requirements