Medication Alerts, Part Two
Checking the schedule and handling callbacks
Issue: 14.1 (January/February 2016)
Author: JC Cruz
Author Bio: JC is a freelance writer based in British Columbia. He is a regular contributor to
Article Description: No description available.
Article Length (in bytes): 55,859
Starting Page Number: 45
Article Number: 14108
project14108.zip Updated: 2016-01-04 10:40:44
Related Web Link(s):
Excerpt of article text...
In my last article, I introduced the concept of medication alerts. I also introduced the concept of a common alerts module, demonstrated how to implement it and how to use it in health forecasting and medication tracking.
Now, I shall complete implementing medication alerts. I shall explain the purpose of dosage schedules and why they have to be followed. I shall show how to perform schedule checks, how to handle alert callbacks, and how to maintain a history of medication alerts.
An updated version of the FooHealth project (Mk6) is available from the magazine's website. Readers must have a working knowledge of Xojo/REALbasic.
Dosage Schedules, An Indepth Look
Some user-patients take their medications on demand, some according to a specific schedule. In the former case, they do so in response to a condition or symptom. For example, if the user-patient has a headache, she might take an analgesic. If she has a case of diarrhea, she might take an anti-motility.
In the latter case, user-patients take their meds at prescribed intervals. Sometimes, these intervals are set by the health provider. Other times, they are set by the pharmacist. Whatever the case, dosage schedules are not set at random or on a whim. In fact, they are set according to something called a half-life.
...End of Excerpt. Please purchase the magazine to read the full article.