About using RT-SA object to display waveform

[wei hou]

Hi

I'm using antidote library for developing ecg device application.

But I don't know how to use RT-SA class to display waveform.

In ieee 11073-10406 profile , E.4.1.2 APDU of MDS attributes is not
complete.

RT-SA attribute is not in APDU message.

Now I have a question : Where can find a complete APDU message of MDS
attributes with RT-SA attribute.

[Elvis Pfutzenreuter]

RT-SA support in Antidote is untested. You will be first :)

[wei hou]

Can SigHealth Platform support ecg device and display ecg waveform ?

[Elvis Pfutzenreuter]

Yes, we work with devices with ECG profile objects.

[wei hou]

Thank you for answer !

When ECG agent send extended configuration, What is the config
object count ?
In extended config sample of ieee 11073-10406 profile, it is 2. But
it only have heart rate and R-R interval class, not have ecg scanner
class and attribute list of scanner class.
Can you give me a sample of ecg like this?

0x00 0x13 obj-class = MDC_MOC_SCAN_PERI
0x00 0x28 obj-handle = 40 (Æ measurement i is a Periodic Scanner)
0x0A 0x04 attributes.count = 4
0x00 0x50 attributes.length = 80
0x00 0x53 attribute-id = MDC_ATTR_OP_STAT
0x09 0x02 attribute-value.length = 2
0x00 0x00 disabled
0x00 0x54 attribute-id = MDC_ATTR_SCAN_REP_PD_MIN
0x0A 0x04 attribute-value.length = 4
0x00 0x00 RelativeTime of 333.33 (333.375 exact) msec
0x0A 0x6B
0x09 0x13 attribute-id = MDC_ATTR_CONFIRM_MODE
0x00 0x02 attribute-value.length = 2
0x00 0x00 unconfirmed mode
0x0A 0x53 attribute-id = MDC_ATTR_SCAN_HANDLE_ATTR_VAL_MAP
0x00 0x36 attribute-value.length = 54
0x00 0x04 HandleAttrValMap.count = 4
0x00 0x32 HandleAttrValMap.length = 50

0x00 0x01 HandleAttrValMap 1: SpO2
0x00 0x03 HandleAttrValMap.count = 3
0x00 0x10 HandleAttrValMap.length = 16
0x0A 0x4C MDC_ATTR_NU_VAL_OBS_BASIC, 2
0x00 0x02
0x09 0xAC MDC_ATTR_AL_COND,2
0x00 0x02
0x09 0x47 MDC_ATTR_MSMT_STAT,2
0x00 0x02
0x09 0x90 MDC_ATTR_TIME_STAMP_ABS, 8
0x00 0x08

0x00 0x0B HandleAttrValMap 2: Pulse Rate
0x00 0x01 HandleAttrValMap.count = 1
0x00 0x04 HandleAttrValMap.length = 4
0x0A 0x4C MDC_ATTR_NU_VAL_OBS_BASIC, 2

0x00 0x02 HandleAttrValMap 3: SpO2 – fast-response
0x00 0x01 HandleAttrValMap.count = 1
0x00 0x04 HandleAttrValMap.length = 4
0x0A 0x4C MDC_ATTR_NU_VAL_OBS_BASIC, 2
0x00 0x02

0x00 0x0C HandleAttrValMap 4: Pulse Rate – fast-response
0x00 0x01 HandleAttrValMap.count = 1
0x00 0x04 HandleAttrValMap.length = 4
0x0A 0x4C MDC_ATTR_NU_VAL_OBS_BASIC, 2
0x00 0x02

In MDS attribute,there is not RT-SA attribute too. Could you also
give me a simple ?

Thank you very much.

[Elvis Pfutzenreuter]

The ECG specialization devices that I have worked with, don't use
RT-SA (they are heart rate sub-specializations), so I don't have an
example specifically for RT-SA.

[wei hou]

Thank you for answer.

But I gotta ask that what the manufacturer and product name of your
ECG specialization device is ,

and which specializations not IEEE 11073-10406 it used.

Did it use SCP-ECG or HL7 aECG ?

Which kind of data struct ( not RT-SA ) to represent the waveform ?

[Elvis Pfutzenreuter]

It is transcoded from Bluetooth Low Energy, so it follows the Transcoding
Whitepaper spec.

[wei hou]

Is the measurement data passed  to the application layer still in the
XML format of Antidote?
if so, could you give me the XML file of the ECG data and its MDS
attribute?
Thanks!

[Elvis Pfutzenreuter]

I got this from the developer that worked with the device:

Device Configuration
[{"meta_data": [{"name": "HANDLE", "value": "1"}], "compound": {
"name": "Numeric", "entries": [{"compound": { "name": "Type",
"entries": [{"simple": {"name": "code", "type": "intu16", "value":
"16770"}}, {"simple": {"name": "partition", "type": "intu16", "value":
"2"}}] }}, {"simple": {"name": "Metric-Spec-Small", "type": "intu16",
"value": "32896"}}, {"simple": {"name": "Unit-Code", "type": "intu16",
"value": "2720"}}] }}, {"meta_data": [{"name": "HANDLE", "value":
"2"}], "compound": { "name": "Numeric", "entries": [{"compound": {
"name": "Type", "entries": [{"simple": {"name": "code", "type":
"intu16", "value": "16168"}}, {"simple": {"name": "partition", "type":
"intu16", "value": "2"}}] }}, {"simple": {"name": "Metric-Spec-Small",
"type": "intu16", "value": "34944"}}, {"simple": {"name": "Unit-Code",
"type": "intu16", "value": "6848"}}] }}]

Measurement Data
[{"meta_data": [{"name": "HANDLE", "value": "1"}], "compound": {
"name": "Numeric", "entries": [{"meta_data": [{"name": "partition",
"value": "2"}, {"name": "metric-id", "value": "16770"}, {"name":
"unit-code", "value": "2720"}, {"name": "unit", "value": "bpm"}],
"simple": {"name": "Simple-Nu-Observed-Value", "type": "float",
"value": "0.000000"}}, {"compound": { "name": "Absolute-Time-Stamp",
"entries": [{"simple": {"name": "century", "type": "intu8", "value":
"20"}}, {"simple": {"name": "year", "type": "intu8", "value": "13"}},
{"simple": {"name": "month", "type": "intu8", "value": "1"}},
{"simple": {"name": "day", "type": "intu8", "value": "29"}},
{"simple": {"name": "hour", "type": "intu8", "value": "15"}},
{"simple": {"name": "minute", "type": "intu8", "value": "35"}},
{"simple": {"name": "second", "type": "intu8", "value": "22"}},
{"simple": {"name": "sec_fractions", "type": "intu8", "value": "0"}}]
}}] }}]


2013/1/27 wei hou <houw...@gmail.com>:

--
Elvis Pfützenreuter
Senior Architect, Connectivity
e...@signove.com
p: +55 83 3321 6367
c: +55 47 8801 6105
--------------------------------------------------------------------------
CONFIDENTIALITY NOTE: This e-mail is intended only for the person or entity
to which it is addressed and may contain information that is privileged,
confidential or otherwise protected from disclosure.