Measurements are a part of every person’s life. During a run in the park the hearth frequency is measured, the track is traced and the walk distance recorded. After the run it’s possible to get the latest information: Was the last run faster, efficiently or are the goals missed? For all this conclusions a lot of different measurements have to be recorded and handled.


CGM LIFE provides are measurement data type to handle lots of different measurements from biometric values to fitness and nutrition data.

Measurements -  Description

For a detailed description of the special measurement types please have a look at the concrete data model descriptions of the different types.

Usually measurements describe values measured at a specific point in time. This point in time can be in the past or right now. Besides CGM LIFE also offers the opportunity to record values for a period in time, e.g. walk distance. For computed values it’s possible to store also meta information (e.g. calculation formula, source) as part of the measurement object.


The use of the measurement object varies from measurement type to measurement type. Therefore it is necessary to have a detailed look at the concrete data model description to use the data type in the correct way.

Not use

As described above all measurement types should be used in a specific way and hence also the not use is different and can be found in the concrete data model description. The measurement object itself is not used directly.

Data Model

Name Type M Description Example
parameterCode CodedEntry X The parameterCode defines the name and further catalog information in combination with the concrete code (e.g. LOINC) for the observed parameter. “parameterCode”:{“catalogName”: “LOINC”,“catalogVersion”: “2.48”,“code”: “8308-9”,

“codeText”: “LOINC 8308-9”,

“description”: “Body height –standing”}

startDate DateTime The startDate defines the point in time when the measurement is executed, e.g. weight, or the beginning of a period, e.g. steps. “2014-05-09T08:01:07.143”
endDate DateTime The endDate is only needed in case of using a timespan and defines the end of the measurement period. “2014-10-14T11:24:55.143”
value UnitValue X The value is the measured value and the belonging unit. “value”: {“value”: 70,”unit”: “kg”,”valueText”: “70 kg”}
informationSource CodedEntry The informationSource describes the source of information for a better evaluation of the quality of data. “informationSource”: {“code”: “ProvidedByPatient”,”codeText”: Information provided by patient”}
calculationFormula String In case of calculated data, e.g. BMI, the formula of calculation should be specified to check the validity of the value. “BMI = x KG / (y M * y M)”
comment String See general data model description. “This is a comment”
device Device The device is an inherited object to describe the device used for the measurement. See device for example.


The rules are based on the concrete data model and can be found in the description of the types.

Parameter Codes

For all measurements a list of recommended LOINC codes is described in the concrete data model.


The information source is based on a coded entry. Therefore it is possible to deposit different catalogs.

In the case of not using a standard catalog the following list gives a list of possible entries with name and code/ID.

Code/ID Name
MeasuredByPhysician Measured/assessed by physician
MeasuredByStaff Measured/assessed by staff
ProvidedByPatient Information provided by patient
measuredByTelemedicineDevice measuredByTelemedicineDevice
OtherInformationSource Other information source
UnknownInformationSource Unknown information source
MultipleInformationSources Multiple information sources


External catalogs: LOINC 2.48

Internal catalogs: CGM LOINC add-on

Update Rhythm

As described before every type of measurement varies in its use. Therefore also the update rhythm is special for every type.  Please have a look at the concrete data model description.


“id”: “/core/Measurement”,
“$schema”: “”,
“type”: “object”,
“properties”: {
“parameterCode”: {
“$ref”: “/core/CodedValue
“startDate”: {
“$ref”: “/core/DateTime
“endDate”: {
“$ref”: “/core/DateTime
“value”: {
“$ref”: “/core/UnitValue
“informationSource”: {
“$ref”: “/core/CodedValue
“calculationFormula”: {
“type”: “string”
“comment”: {
“type”: “string”
“device”: {
“$ref”: “/core/Device
“required”: [
“additionalProperties”: false

Compatible Standards

The measurement objects are compatible to EHR and TenScan. For details please have a look at the concrete data models.