CS 2310 Project— Just-in-Time Medical Application

Matching between IC Card and IC System in MKEE

Zhoulan Zhang (zzl@cs.pitt.edu)

I. IC Card

1.1 IC Card and IC Card Editor Structure

The IC Card Editor enables efficient editing of IC cards (Figure 1). It is also a good tool to organize and manage IC cards. As shown in Figure 2, under the IC Card Editor environment, an icCardList maintains a list of icCardEntry, each with a unique id, along with a group id indicating which group it belongs to.

For each icCard, it includes the following attributes:

l icName— IC name.

l icDescription— Description for the IC

l icIntPattern— Interaction Pattern, can be one of the six patterns (grey, green, yellow, orange, red, and purple)

l icMyTask— Task of current IC

l icTimeCriticalCondition— Time Critical Condition

l icOtherName— Name of Other IC which current IC will communicate with

l icOtherMessage— Message sent to Other IC

l icOtherTask— Other IC’s Task

l icNumberCurrent— i, the ith IC card (if use n IC cards to describe current IC)

l icNumberTotal— n, the total number of IC cards to describe current IC

Figure1. IC Card

Figure2. IC Card Structure

1.2 IC Card XML schema

The following is an example of IC Card XML schema used by IC Card Editor. All attributes mentioned above are set to certain values.

<icTimeCriticalCondition content="Tc+Talarm > Ts > Tc+Tnormal: Talarm=2*smallest system granularity, Tnormal=smallest system granularity" />

</icCard>

II. IC System Structure

2.1 IC System in MKEE

In MKEE (Multimedia Knowledge Eclipse Environment), the Index Cell is a little different from the IC depicted by IC Card. It can give more details than IC Card does (Figure 3 is an example of Index Cell and its specifications). The details for attributes are explained below:

Figure3. Index Cell in MKEE

Each Index Cell has such properties:

n Current State

n Id

n Max Life time (cell life time, if you want a cell to be always active, set it to “inf”)

n Name

n Type

An Index Cell may have different states. To transform from one state to another state inside of an index cell, a transition will be used. The transition properties include:

n Id

n Source: initial state

n Target: final state

n Type ( can be “Boundary” or “Internal”)

A transition can include input message, output message, and actions.

The Input message has such properties:

n Id

n Name

n Predicate (it’s the condition that establishes the state change)

Output message properties include:

n Id

n Name

n Target IC

Both input message and output message can carry parameters. A parameter should state:

n Name

n Data Type

n Data Value

Besides input message and output message, a transition involves action. The action properties are:

n Id

n Name ( the name of output message name)

n Body ( action associated to the transition)

n Target ( it could be either “external” or “source”)

- external: the action doesn’t directly work on multimedia system, but it shows itself through computations

- source: the action works on multimedia system without any computation

2.2 IC System XML Schema

In MEKK, there is an XML file corresponding to each IC diagram. The following is an example of the XML schema used by MKEE IC diagram:

<?xml version="1.0" encoding="UTF-8"?>

<ic:icSystem xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ic="http://www.mke.org/ic/">

</message>

</transition>

</indexCell>

……

</ic:icSystem>

III. Matching between IC Card and MKEE IC System

Although there are some differences between IC Card and IC System designed using the MKEE tool, there are many similarities. Especially both of them can be represented by XML, which is human-legible and facilitates the sharing of data across different information systems.

Matching can be summarized as the following (also shown in Figure 4)

Entries in IC Card Editor	Attributes in IC System by MKEE
icCardEntry.id	id
icCard.icName	name
icCard.icTimeCriticalCondition	time parameter in messages
icCard.icOtherName	the target Index Cell of output message
icCard.icOtherMessage	message sent to other Index Cell (target IC)
icCard.icMyTask/icCard.icOtherTask	action in transition (internal/external)

n icCardEntry.id = id;

Every icCardEntry has a unique id, since in IC System each Index Cell should also has a unique identification (id), these two can be simply regarded as the same.

n icCard.icName = name;

To make it compatible, the IC name used in IC card is the same as in IC System.

n icCard.icTimeCriticalCondition = time parameter in messages

In an IC Card, users can add timing constraints, indicating the time during which a task should be done. In IC System, similar timing constraints can be imposed, however, through the parameter in messages. As mentioned earlier, both an input and output message can carry parameters, time is one type of the parameters and can meet the just-in-time requirement.

n icCard.icOtherName = the target Index Cell of output message

In an IC card, if a message will be sent to other ICs, the entry “icOtherName” should be the name of the IC which the current IC wants to communicate with. In IC System, it is just the target index cell of output message.

n icCard.icOtherMessage = message sent to other Index Cell (target index cell)

Note that there are two message types in IC System: input message and output message. Since the message mentioned here is sent to another Index Cell, it is of the output message type.

n icCard.icMyTask/icCard.icOtherTask = action in transition (internal/boundary)

q icMyTask à internal

If the current IC needs to do some task all by itself, the target of action in transition is internal, meaning the transition just associates with its own states, having nothing to do with other ICs.

q icOtherTask à boundary

If the current IC needs other IC to accomplish some task, then the target of action in transition is of boundary type.

q icCard.icIntPattern is also associated with action in transition.

For example, for a purple IC card, both internal and external actions will be shown in the Index Cell in IC System.

Figure4. Matching between IC Card and IC System in MKEE

IV. Conclusions

The XML matching between IC Card (in IC Card Editor) and IC System (in MKEE) suggests that these two tools are compatible.

Appendix

IC System Design for Non-Able Patient & the XML Presentation

<?xml version="1.0" encoding="UTF-8"?>

<ic:icSystem xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ic="http://www.mke.org/ic/">

</message>

</transition>

</indexCell>

</message>

</transition>

</indexCell>

</message>

<predicate>threshold reached</predicate>

</message>

</transition>

</indexCell>

<predicate>alert msg received</predicate>

</message>

</message>

</message>

</transition>

</indexCell>

<predicate>patient's alert and current condition received</predicate>

</message>

</message>

</transition>

</indexCell>

<predicate>dispatch request received</predicate>

</message>

</message>

</transition>

</indexCell>

</ic:icSystem>