Dr. Sim

See the following -

Open mHealth Popular Standard (Part 2)

Andy Oram | EMR & EHR | December 2, 2015

Normally, one wants to break information down into chunks as small as possible. Bydoing this, you allow data holders to minimize the amount of data they need to send data users, and data users are free to scrutinize individual items or combine them any way they want. But some values in health need to be chunked together. When someone requests blood pressure, both the systolic and diastolic measures should be sent. The time zone should go with the time. On the other hand, mHealth doesn’t need combinations of information that are common in medical settings. For instance, a dose may be interesting to know, but you don’t need the prescribing doctor, when the prescription was written, etc. On the other hand, some app developers have asked the prescription to include the number of refills remaining, so the app can issue reminders.

Read More »

Open mHealth Popular Standard (Part 3)

Andy Oram | EMR & EHR | December 3, 2015

The first section of this article introduced the common schemas for mobile healthdesigned by Open mHealth, and the second section covered the first two design principles driving their schemas. We’ll finish off the design principles in this section. Here, the ideal is to get accurate measurements to the precision needed by users and researchers. But many devices are known to give fuzzy results, or results that are internally consistent but out of line with absolute measurements. The goal adopted by Open mHealth is to firm up the things that are simple to get right and also critical to accuracy, such as units of measurement discussed earlier. They also require care in reporting the time interval that a measurement covers: day, week, month. There’s no excuse if you add up the walks recorded for the day and the sum doesn’t match the total steps that the device reports for that day...

Read More »