METODOLOGÍA DE LA INVESTIGACIÓN
Módulo 3 sobre EdC 10 Creencias sobre cuestiones ligadas a la
4.3.6 Sistemática de contexto para EdC
The top level model shows the primary components of the system along with the transitions between them. The purpose is to capture the top level
resource/information flow between the principle components. This helps overall system decomposition and function allocation. Similarly, the function
decomposition is performed for each of the functional component and respective transactions documented in a tabular form.
102
Figure 3-19 Resource Flow - Network Model Table 3-8 Transitions for System Flow Model
Transitions Explanation Notes
T1-1 Instrument registration, data submission and possible requests from the Instrument node to the Instrument Data Management Node.
Raw data acquisition T1-2 Data publication and Commands from the Instrument
Management Node to the Instrument. Raw data acquisition T1-3 Data publication from the Data Management Node
to the Knowledge Repository (engine) Knowledge acquisition T2-1 Clinic registration, Clinical data submission and
possible requests from the Instrument node to the Clinical Data Management Node.
Clinical data acquisition T2-2 Clinical data publication and Commands from the
Clinical Data Management Node to the Clinic. Clinical data acquisition T2-3 Clinical data publication from the Clinical Data
Management Node to the Knowledge Repository (engine)
Knowledge acquisition T3-1 User registration and data submission from user node
to the User Data Management Node. User data acquisition T3-2 User data publication and Commands from the
Instrument Management Node to the User. User data acquisition T3-3 User data publication from the User Data Knowledge
103
Management Node to the Knowledge Repository
(engine) acquisition
TA-1 Publication of analytical results to knowledge engine for the following capabilities:
Event modeling Event predication Event diagnostics
Analysis and decision
TK-1 Publication of events to the user, clinic and sensor tasking. The transactions for each category are further explained for each respective node.
Knowledge dissimilation
3.13.3.1 Instrumentation Node
Figure 3-20 Resource Flow - Instrument Node Model
Create the logical representation of an instrument. The instrument node is represented by a series of logical device. Each device is further decomposed to logically accessible nodes.
Table 3-9 Transitions for Instrument Node Transitions Description
D-1 Registration of logical device to an instrument Data report from the logical device to instrument D-2 Commands from the instrument to a logical device
104
D-3 Registration of logical node to a logical device Data report from the logical device to instrument D-4 Commands from the logical device to node D-5 Registration of physical device to node
Data report from physical device to respective node D-6 Commands from the logical node to physical device
3.13.3.2 Instrumentation Data Management Node
Figure 3-21 Resource Flow - Instrument Data Management Node Table 3-10 Transitions for Instrument Data Management Transitions Description
T1-1
(Commit Data)
This transaction is invoked either periodically at a given interval. It can also be executed upon receiving abnormal readings. This is a push mechanism from the instrument (sensor) to the instrument data store.
T1-2
(Task Sensor)
This transaction is executed when abnormal data is reported by the sensor. The Sensor Data Management Node has the option to task the sensor/instrument to re-sample if possible. This is a push mechanism from the instrument data store to the individual instrument to perform functions.
Validate This transaction represents the “data scrubbing” process, where the data is validated to minimize faulty sensors or erroneous
105 entries.
3.13.3.3 Clinic Node
The following diagram establishes the resource flow between the Clinic Node and the principle actors for the purchase of taking care of the patient’s needs.
Figure 3-22 Resource Flow Clinic Node Table 3-11 Transitions for Clinic Node Transitions Description
CT-1 Transaction represents the patient registration with the clinic node.
CT-2 Transaction represents the clinic node push information to the patient node. This generic data push could be: data publication
106
or patient assignment notification.
CT-3 Data publication from the clinic node to a doctor. This generic data push can be ranging from notification of patient data to re-assignment of a patient.
CT-4 Data publication from a doctor to the clinic node. An example use of this transition can be one of the following:
Doctor registration with the clinic node Recording of diagnostic information Patient information entry
Patient prescription information
CT-5 Data publication from the clinic node to a nurse. This generic data push can be ranging from notification of patient data to
re-assignment of a patient.
CT-6 Data publication from a nurse to the clinic node. An example use of this transition can be one of the following:
nurse registration with the clinic node entry of observation information patient care information/record
CT-7 Data publication from the clinic node to a clerk. This generic data push can be ranging from notification of patient presence
information to financial transactions.
CT-8 Data publication from a clerk to the clinic node.
3.13.3.4 Clinical Data Management Node
107
Figure 3-23 Resource Flow Clinic Data Management
Table 3-12 Transitions for Clinic Data Management Transitions Description
T2-1 This transaction decomposes the data submission from the clinic node into the domain centric data store: clinic, doctor, diagnostic and patient information centric.
T2-1-1 Transaction specifically targets user centric information such as financial data etc. A potential use is user data informatics.
T2-2 Transaction targets any potential user information change. It creates the automatic data triggering mechanism for clinic based notification.
T2-2-1 Transaction enables the clinic to be centrically tasked by the knowledge engine, where better collaboration and resource management can take place.
3.13.3.5 User Node
The following diagram displays the resource flow for a user with respect to session. This design allows the user to assume multiple roles within the context of
108
a session. For example, a user can be doctor while at the same time being the patient depending on the context of the session.
Figure 3-24 Resource Flow - User Node
Table 3-13 Transitions for User Node Transitions Description
U-1 Transaction to associate a user with a role within the system.
U-2 Role specific data and access for the user
U-3 Transaction to associate the role with the context of a current session.
U-4 Contextual specific data push to the role
U-5 Transaction to associate the context with an actual on-going session.
U-6 Session specific data push to the context
109
3.13.3.6 User Data Management
Figure 3-25 Resource Flow - User Data Management Table 3-14 Transitions for User Data Management Transitions Description
Notify User Data push performed by the user data management node to notify the user of information from the system.
Submit Data This transaction is invoked either periodically at a given interval. It can also be executed upon receiving abnormal readings. This is a push mechanism from user to the data store.
Validate User information data validation and possible correlation with the information within the data system for error detection and /or corrections.
110
3.13.3.7 Analysis Engine
Figure 3-26 Resource Flow - Analysis Engine
Table 3-15 Transitions for Analysis Engine Transitions Description
A-1 Automatically pull data from the data store for the following purpose:
Event detection Data Modeling
Data Visualization (on demand)
A-2 Automatic transition upon detect of an event to perform event classification.
A-3 Transaction to determine possible course of actions.
A-4 Transaction to perform event prediction based on the classification information
A-5 Transition to initiate event specific visualization.
A-6 Transition to commit the reduced data set back into the data store.
111
3.13.3.8 Knowledge Engine Node
Figure 3-27 Resource Flow Knowledge Engine
Table 3-16 Transitions for Knowledge Engine Transitions Description
K-1 Transition to perform resource de-confliction and allocation. The system shall adjust the work flow and task assignment based on the patients’ needs and the availability of the care providers.
K-2 Transaction to combine the sensing information and patients’
historical information to perform out break forecasting.
K-3 Transaction to perform historical sensor data and information management.
K-4 Transaction to automatically provide forecast notifications to potentially impacted users.
K-5 Transaction to automatically task sensors
K-6 Transaction to automatically notify patient of the assignment once the care provider accepts the new allocation.
112
3.14 Architecture and Data Model Product Overview
This section describes the structure of an architecture domain’s system data types and the structural business process rules (defined in the architecture’s OV) that govern the system data. It provides a definition of architecture domain data types, their attributes or characteristics, and their interrelationships.