HealthVault Data Types

Type Preview: Medication

We have had a number of requests from partners to revise the Medication data type, and this post describes our current thoughts in this area. We would like to have your feedback on whether this meets your needs and works well for your scenarios. We are also interested in whether the descriptions provide sufficient information to understand what each field stores.  Finally, if there are specific vocabularies that you want to use for codable values in these types, please add a comment with those as well.

There are currently two types related to medication in HealthVault - there is the Medication type and the Daily Medication Usage type. 
 
We are proposing breaking medication into three types:
 
The Medication type is used to store information that answers the question "What medication is the record owner taking, and why?" For example, a person might be taking 75mg of aspirin daily to help prevent heart disease, 20mg of a statin drug twice a day to reduce cholesterol, and a One-A-Day Men's Health Formula multivitamin. This type is intended to support information entered directly by a person, or from a clinical system.
 
The Medication Prescription type is used to store information about a specific prescription, and is the analog what you get when you pick up a prescription from a pharmacy (ie the medication and some of the information on the instruction sheet).
 
While Medication and Medication Prescription are intended to be related (using related items) if they both come from an electronic system, they contain sufficient information to stand alone. They therefore both contain information about the specific medication, and the dose/strength/frequency of the medication.
 
The Medication Fill type stores information about the act of filling the prescription. It will always be related to a specific prescription. 
 
In addition to these three types, the Daily Medication Usage type will be used to track the administration of the medication. That type is not described in this post. 

Medication:

Some of the existing fields are moved to the Medication Fill type, and fields such as dose & dose unit are replaced with a field named "dose", which is of the "general measurement" type (see below for more information on general measurement).

Element  Type Description
Name string Patient-understandable name for the medication
Code Codable value Code/codes for the medication. Vocabs include RxNorm, NDC
Date-discontinued Approx-date Date the patient stopped taking the medicine
Date-started Approx-date Date the patient started taking the medication
Prescribed Codable value Whether the medication is prescribed, self-prescribed, etc.
Indication String Why the patient is taking medication
Dose General measurement Patient-understandable dose plus structured value and unit.
Examples: 1 table, 50ml
Strength General measurement Patient-understandable strength plus structured value and units.
Examples: 25mg, 15mg/ml
Frequency General measurement Patient-understandable frequency plus structured value and units
Example: Once a day
Route Codable value The route of the medication. Vocab=medication-routes.
PrescribedBy  Person The physician who prescribed this medication Person

Medication Prescription:

Contains the relevant information for a prescription. The information here is focused on the patient's view of the prescription, not the pharmacy's or the physician's view. 

Element  Type Description
Name string Patient-understandable name for the medication
Code Codable value Code/codes for the medication. Vocabs include RxNorm, NDC
Date-prescribed Approx-date Date the medication was prescribed
Amount-prescribed General measurement The amount prescribed
Prescribed Codable value Whether the medication is prescribed, self-prescribed, etc.
Dose General measurement Patient-understandable dose plus structured value and unit.
Examples: 1 table, 50ml
Strength General measurement Patient-understandable strength plus structured value and units.
Examples: 25mg, 15mg/ml
Frequency General measurement Patient-understandable frequency plus structured value and units
Example: Once a day
Route Codable value The route of the medication. Vocab=medication-routes.
Substitution Codable value Whether the medication should be dispensed as written or whether substitution is allowed.
Duration General measurement Patient-understandable duration plus structured value and units
Refills Non-negative integer Original number of refills
Days-Supply Non-negative integer Number of days supply
Prescription duration Duration-value The duration of the prescription
Instructions String Instructions that go along with the prescription
Prescription Number String Prescription Number
PrescribedBy Person The physician who prescribed this medication

Mediation Fill

Records the act of filling or refilling a prescription.

Element  Type Description
Name string Patient-understandable name for the medication
Date-filled Approx-date Date of this fill
Refills-left Non-negative integer The number of future refills that are allowed.
Days-Supply Non-negative integer Number of days supply
Pharmacy Organization The pharmacy that filled the prescription
Prescription Number String Prescription Number

General Measurement

The general measurement type is somewhat analagous to the codable value type. It contains a "display" field, which contains a user-readable value, and also one or more value & unit pairs, where the value is a double and the unit is expressed as a codable value.

A dose of 200 mg would be stored as follows:

display: "200 mg"
value: 200
units: mg, coded from the measurement-units vocabulary

Published Monday, May 12, 2008 1:25 PM by ericgu
Filed under:

Comments

 

bhurter said:

Consider including:

Generic indicator, generic drug name, brand name (if prescribed), along with the fill strength and instructions as dispensed.  This can be different from the "as prescribed" medication.  For example:

"As Prescribed":  Advil, 800MG take 1 tablet every 8 hours

"As Filled":  Ibuprofen, 400MG take 2 tablets every 8 hours

May 14, 2008 12:40 AM
 

Jared Roach said:

I think the "general measurement" needs to allow ranges; I was not sure if it currently does. For example,

"take 1 to 4 tablets every 4 hours depending on level of pain" or "take 10-50mg every night".

Should think about how to include a taper: "Take 50 mg on day 1 and 2, then 25 mg for 4 days, then 10 mg for 4 days, then 5 mg for a week, then stop"

Is "compliance" a useful field for one or more of these data types? Compliance is slightly different than administration record. A patient might report (or be judged) to have taken about 85% of prescribed doses. They may not remember exactly which ones. But this field wold probably be very rarely used.

Spelling in original post: table -> tablet; mediation -> medication

I agree with the comments by bhurter, above. But maybe all the synonyms for a medication (generic, brand name, colloquial, and otherwise) can be stored in another table, so only one of these synonyms (as long as unique) need be put into the code field (I am assuming the code field is where the unique name of the med goes).

Great HealthVault Meeting yesterday, and lecture on data types!

June 11, 2008 5:28 PM
 

Jared Roach said:

I am not sure if conditional dosing (particularly used for insulin) is covered:

if glucose >240 take 20 units

if glucose >200 < 240 take 15 units

if glucose >100 < 200 take 10 units

if glucose >50 < 100 take 5 units

if glucose < 50 take no units (and take some other action as well)

I suppose this must be supported as there are a number of HV applications that support glucometers...(?)

June 11, 2008 7:04 PM
 

HealthVault Data Types said:

We’ve gotten some good feedback on our proposed data type design, and we have a new one to run by you.

June 26, 2008 5:55 PM
New Comments to this post are disabled

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker