Conceptual Approach
is a new generation Medical Information System, powered by an innovative approach to medical knowledge base. This approach is derived from the notion that medical environments (even within the same specialty or sub-specialty) differs from each other in workflow as well as in the way medical knowledge base is utilized.
Taking all this into consideration, is structured as a generic data engine/platform (rather than a sealed application), that allows each environment to have its Medical Information System tailored and shaped according to its own specific needs – without any programming intervention.
System Data Units and Objects
medical infrastructure consists of data units which can be described as a “Lego” of building blocks
"Lego" of building blocks...
organized in hierarchical order. In software technical terms any building block is an Object that has properties and methods which dictate its generic “Behavior”. All those objects are user pre-defined via a knowledge base definition sub-system running offline as a separate executable. This sub-system is used by authorized professional decision maker, to accommodate medical knowledge base, clinical policy and workflow, according to their very specific needs. There is no limitation to the number and combination of the Data Elements that can be defined for a given knowledge base.
knowledge base is stored in an XML document, where all data elements are stored and organized hierarchically in a top down order.
The primary hierarchy layout consisting of the following data elements:
Knowledgebase Data Elements hierarchy
Visit – Is the top element and it consists of a Protocol
Protocol - Consists of Groups and is associated with a Visit Type
Groups - Are logical data units consists of basic data elements
Basic Elements - TESTS, DIAGNOSIS, TREATMENTS and DRUGS
Typical Customization
is shipped with several types of predefined knowledge base suits that can be modified and fine-tuned to support various ophthalmology sub-specialties, clinic medical guidelines policy and workflow.
In principle a clinic can use the Data-Definition-Engine to have its knowledge base build up from scratch; however in real life clinic usually will use one of the predefined suits as its take-off point for modifications.
Typical customization focus usually on following data elements:
- Create Visits Type List
- Modify the TEST list
- Generate GROUPS that  clusters TESTS in logical units
- Create PROTOCOL that associates with the Visits Type
- Modify/Define PHRASES and NORMAL VALUES
- Associate PHRASES and NORMAL VALUES with Basic Elements – TESTS, DIAGNOSIS, TREATMENTS, DRUGS