CoPilot 4.1 - data import and export.pdf
(
1648 KB
)
Pobierz
Importing TAB and XML Data
Importing TAB and XML Data
About TAB and XML Imports
The CoPilot Health Management System program provides functions to import and export data in
the following two formats:
1.
TAB – Tab Delimited Text
2.
XML – Extensible Markup Language
These formats are used within the program to support archiving but they may also be used to
import data from external sources that would not otherwise be supported by the CoPilot program.
Import Capabilities
The import functions of the CoPilot program are limited to the following event data types:
Exercise Data
Glucose Data
Basal Insulin Data
Bolus Insulin Data
Lab Results
Meal Information
Medical Exam Results
Medication
Notes
State of Health
Ketone Data
Alarm Events
Generic
Required Skills
The user will be required to have suicient technical skills to be able to manipulate or create data
iles as outlined in this document. File imports of this sort should not be undertaken by users who
do not have a full understanding of the formatting requirements.
Caution –
The user must check the data for appropriate formats before importing the data into
CoPilot.
File Formats
For the purposes of simplifying the documentation and basic understanding of the import
functions, this document concentrates on how to format the data for TAB ile imports. There
are many similarities between the TAB and XML formatting requirements. The speciic XML
requirement diferences are included at the end of this document under
XML Standards
section.
DOC14109 Rev. A 03/08
1
Importing TAB and XML Data
There are many methods available to create acceptable TAB import iles for CoPilot. Most of the
example information in this document assumes that users will develop the import iles in Excel.
The following are the two limitations associated with Excel:
Under some circumstances, Microsoft Excel may add illegal quotation marks around
ield entries when a ile is saved. This occurs when commas or other common delimiter
characters are included as part of the data. The user must remove these quotation marks
prior to importing a ile into CoPilot.
2.
In order to avoid diferences in values and times, when converting back and forth between
Microsoft Excel and CoPilot, it is required that all values in Microsoft Excel shall be handled
with full double-precision accuracy. This can be accomplished in Microsoft Excel by setting
the cell formatting of these numbers to at least ten decimal places.
File Structure
A CoPilot TAB import ile is a lat, ASCII text ile composed of records arranged physically in rows.
Each row constitutes the complete entry for a single data event.
Each row is made up of several deined data ields with each ield separated by a TAB character
(ASCII 09). Each row is terminated by an ASCII carriage return and/or line feed.
File Type
A TAB import ile must have the ilename extension
.TAB
. An XML import ile must have the
ilename extension
.XML
.
DOC14109 Rev. A 03/08
2
1.
Importing TAB and XML Data
Header Row
The import ile must have a header row, which is the irst row in the ile. The header row must
include all of the following ield labels, exactly as presented below, and separated by TAB
characters:
DATEEVENT
TIMESLOT
EVENTTYPE
DEVICE_MODEL
DEVICE_ID
VENDOR_EVENT_TYPE_ID
VENDOR_EVENT_ID
KEY0
KEY1
KEY2
I0
I1
I2
I3
I4
I5
I6
I7
I8
I9
D0
D1
D2
D3
D4
C0
C1
C2
C3
C4
C5
C6
C7
C8
C9
ISMANUAL
COMMENT
DELETED
DOC14109 Rev. A 03/08
3
Importing TAB and XML Data
Data Rows
Each row following the Header row must contain data corresponding to the header ields. In some
cases, ields may be empty but TAB characters must still be inserted to separate the ield locations.
Data Fields
There are two diferent types of ields in each data row: Constant Data Fields and Event Type
Dependent Data Fields. All ield values are ASCII character text, but some ields must be numeric
(made up of numerals that can be interpreted as an integer or loating point numbers). CoPilot
handles formatting and wrapping of text, so it is not necessary (or advised) to include carriage
returns or line feeds within text ields. Unused “C” ields (C1, C2, C3, etc.) may be left empty.
Unused “I” ields or “D” ields (I0, i1, D2, etc.) must be set to the numeral zero.
Constant Data Fields
The following ields are associated with every data record and their format is consistent, regardless
of event type.
DATEEVENT
The DATEEVENT ield contains the date and time of the event being recorded. The ield is
a double-precision loating point number that can be converted to a Microsoft Windows
compatible date.
By convention, the integer portion of the number represents the number of days since
the seed, or starting date, of the set. In this case, the seed date, having a value of zero, is
December 30, 1899 12:00 AM. The fractional part of the date value is the portion of the day
that has elapsed.
Example:
0.5 represents December 30, 1899 12:00:00 PM.
TIMESLOT
Most data entered into CoPilot is associated with a time period or time slot. The values
entered in this ield must be integers, according to the following scheme:
Pre-Breakfast = 0
Post-Breakfast = 1
Pre-Lunch = 2
Post-Lunch = 3
Pre-Dinner = 4
Post-Dinner = 5
Bed Time = 6
Sleep = 7
To have CoPilot enter a time slot based on the user’s time period preferences for the given
event time, set the TIMESLOT value to -1. Refer to
Meal
EVENTTYPE
section for additional
information on assignment of TIMESLOT values.
DOC14109 Rev. A 03/08
4
Importing TAB and XML Data
EVENTTYPE
Event types are entered as integers according to the following scheme:
Exercise = 0
Glucose = 1
Basal Insulin = 2
Bolus Insulin = 3
Lab Results = 4
Meal = 5
Medical Exams = 6
Medications = 7
Notes = 8
State of Health = 9
Ketone = 10
Alarms = 15
Generic = 16
Note –
Event types = 11, 12, 13 & 14 are reserved.
DEVICE_MODEL
The DEVICE_MODEL ield is a string data type with a maximum length of 64 characters. This
ield must be populated with the name (description) of the device from which the imported
data was generated. If an import ile is prepared containing data from a source that may
also be directly uploaded or imported into CoPilot, the description must exactly match the
description used in CoPilot. Otherwise, CoPilot’s ability to ilter using this data will be limited.
When multiple instances of import iles are developed that contain data from the same device,
precautions must be taken that the DEVICE_MODEL is identical in each instance. Filtering
based on DEVICE_MODEL is case sensitive. For all data to be imported correctly into CoPilot,
this ield must be populated.
DEVICE_ID
The DEVICE_ID ield is a string data type with a maximum length of 64 characters. This
ield must be populated with the speciic unique identiication of the device from which
the imported data was generated (usually the serial number). If an import ile is prepared
containing data from a source that may also be directly uploaded or imported into CoPilot,
the DEVICE_ID must exactly match the ID in CoPilot. Otherwise, CoPilot ability to ilter using
this data will be limited. When multiple instances of import iles are developed that contain
data from the same device, precautions must be taken that the DEVICE_ID is identical in each
instance. Filtering based on DEVICE_ID is case sensitive. For all data to be imported correctly
into CoPilot, the ield must be populated.
DOC14109 Rev. A 03/08
5
Plik z chomika:
poleszuk
Inne pliki z tego folderu:
CoPilot 4.1 - data import and export.pdf
(1648 KB)
CoPilot 4.1 - user's guide.pdf
(10704 KB)
CoPilot 4.1 - getting started.pdf
(5950 KB)
CoPilot_Setup_US_Web.exe
(16695 KB)
Inne foldery tego chomika:
Dokumenty
Galeria
Kaya Bregovic
kursy-poradniki-ksiazki
Mindjet MindManager 2012 Pro v10.0.445
Zgłoś jeśli
naruszono regulamin