...
Name | Existing Y/N | Database Field | Values | Comments |
Drug | Y | Drug.Name |
|
|
Dose | Y | Drug_Order.Dose |
| Need to add additional units in the form of mg/m2 and mg/kg (as the actual dose given at a visit is based on the patients weight) |
Route | Y | Drug.Route | IV, PO |
|
Infusion volume |
|
| Numeric | Values such as 250ml |
Infusion volume units |
|
| Standard liquid units |
|
Infusion liquid |
|
|
| Values need to be configurable via settings (formerly global properties 1.8 and below) |
Time/Infusion Rate |
|
| Free text because values include ranges (ie 15-30) minutes |
|
Frequency | Y | Drug.Frequency |
| Current values plus the addition of as needed |
Cycle |
|
|
| Chemotherapy treatment is administered in cycles, so knowing which cycle a given drug order is for will be useful. |
Classification |
|
| Premedication, Chemotherapy, Postmedication | The classification is necessary for display purposes so that we can prepare sensible patient summaries |
Start Date | Y | Order.start_date |
| For many of the actual chemotherapy drugs the start and stop dates will be on the same day. |
Stop Date | Y | Order.auto_expire_date |
|
|
...
The Concept Drug Management screen will need to be altered to allow for the Route field to be configurable for Concept Drugs.
Settings (formerly
...
Global Properties from platform 1.8
...
downwards)
...
Additions
settings Settings (formerly global properties from platform 1.8 and belowdownwards) (or other configuration mechanisms) will need to be added to store the following.
...