Protocol Management Development
From CaisisWiki
(→Timeline) |
(→Timeline) |
||
| Line 3: | Line 3: | ||
==Schema Items== | ==Schema Items== | ||
==Timeline== | ==Timeline== | ||
| + | |||
| + | ===Relevant Tables=== | ||
| + | *ProtocolMgr_SchemaItems: represents a particular set of items to be collected (collect LabDate and LabResult for Lab Tests) | ||
| + | *ProtocolMgr_Timeline: represents visit | ||
| + | *ProtocolMgr_ItemTimeline: represents a particular set of items on a visit | ||
| + | *ProtocolMgr_PatientItems: a patient's specific particular set of items for a particular date. | ||
| + | *RelatedRecords: used to relate one record to another | ||
===Advanced Scheduling=== | ===Advanced Scheduling=== | ||
| + | Visits which have advanced scheduling are marked in the Protocol Mgmt Timeline table's ItemIntervalType to determine the scheduling. A pipe is used to delimit multiple advanced scheduling features. | ||
| + | |||
| + | '''ProtocolMgr_Timeline''' | ||
| + | |||
| + | *ItemIntervalType: "Recurring", "Dependent Off Treatment", "Recurring|Dependent Off Treatment" | ||
====Recurring Visits==== | ====Recurring Visits==== | ||
| Line 13: | Line 25: | ||
=====Depending on a previous Visit's item===== | =====Depending on a previous Visit's item===== | ||
| - | In this scenario, when a previous is marked as performed, the dependent visits are then scheduled based upon the performed date of the previous visit. | + | In this scenario, when a previous is marked as performed, the dependent visits are then scheduled based upon the performed date of the previous visit, such as Week 3's visit is based on completion of a Pre-Study lab test. |
| + | |||
| + | A Related Record entry is used to mark a visit's dependency on another visit's item. | ||
| + | |||
| + | '''RelatedRecord''' | ||
| + | |||
| + | *DestTableName: "ProtocolMgr_ItemTimeline" - the visit item on which the visit is dependent | ||
| + | *DestPrimaryKey: pri key of visit item | ||
| + | *SrcTableName: "ProtocolMgr_Timeline" - the dependent visit | ||
| + | *SrcPrimaryKey: pri key of the visit | ||
| + | *SrcSystem: "Caisis" - mark that this an internal Caisis relation | ||
| + | |||
| + | |||
=====Depending on a Patient's status===== | =====Depending on a Patient's status===== | ||
In this scenario, when a specified patient's status is entered, these visits will be scheduled based on that new status. | In this scenario, when a specified patient's status is entered, these visits will be scheduled based on that new status. | ||
i.e., A patient is placed "Off Treatment", and will require a final visit. | i.e., A patient is placed "Off Treatment", and will require a final visit. | ||
Revision as of 20:11, 17 February 2011
Contents |
Developer
Schema Info
Schema Items
Timeline
Relevant Tables
- ProtocolMgr_SchemaItems: represents a particular set of items to be collected (collect LabDate and LabResult for Lab Tests)
- ProtocolMgr_Timeline: represents visit
- ProtocolMgr_ItemTimeline: represents a particular set of items on a visit
- ProtocolMgr_PatientItems: a patient's specific particular set of items for a particular date.
- RelatedRecords: used to relate one record to another
Advanced Scheduling
Visits which have advanced scheduling are marked in the Protocol Mgmt Timeline table's ItemIntervalType to determine the scheduling. A pipe is used to delimit multiple advanced scheduling features.
ProtocolMgr_Timeline
- ItemIntervalType: "Recurring", "Dependent Off Treatment", "Recurring|Dependent Off Treatment"
Recurring Visits
A recurring visit is a visit that will occur at a set frequency for a set time period. For instance, a visit may occur every 4 Weeks for 16 Weeks, creating 4 visits.
Dependent Visits
A dependent visit is one which will not be scheduled until a specified actions happens in the system, such as a patient status changing or upon completion of a visit.
Depending on a previous Visit's item
In this scenario, when a previous is marked as performed, the dependent visits are then scheduled based upon the performed date of the previous visit, such as Week 3's visit is based on completion of a Pre-Study lab test.
A Related Record entry is used to mark a visit's dependency on another visit's item.
RelatedRecord
- DestTableName: "ProtocolMgr_ItemTimeline" - the visit item on which the visit is dependent
- DestPrimaryKey: pri key of visit item
- SrcTableName: "ProtocolMgr_Timeline" - the dependent visit
- SrcPrimaryKey: pri key of the visit
- SrcSystem: "Caisis" - mark that this an internal Caisis relation
Depending on a Patient's status
In this scenario, when a specified patient's status is entered, these visits will be scheduled based on that new status. i.e., A patient is placed "Off Treatment", and will require a final visit.
