This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
userzone:userdoc:dates [2014/03/06 18:07] Matijs created |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | A track defines a sequence of surveys and calculates the period when a certain survey should be answered by or for a certain patient. | ||
- | |||
- | These calculations use dates from multiple sources: | ||
- | |||
- | - an answer from a survey | ||
- | - an appointment linked to the track | ||
- | - another round in the track | ||
- | - from the track itself | ||
- | - manual input | ||
- | |||
- | Using the **Next Step engine** you can only use the previous round in the track and answers from that previous round. This speeds up track editing and track calculation and simplifies the structure. | ||
- | |||
- | More complex dependencies are possible using the **Previous Step engine***, where you can use a date from any of the previous rounds for the valid from date and any of the rounds - either later or earlier - for the valid until date. As this is a more complex version of the Next Step engine you can always upgrade to the Previous Step engine, but nor revert back from it. | ||
- | |||
- | In both engines the valid from date of the first round cannot be dependent on a previous round, so the date should either be calculated from an appointment or from a track level date. | ||
- | |||
- | ==== An answer from a survey ==== | ||
- | |||
- | Every survey has a completion date that can | ||
- | |||
- | ==== An appointment linked to the track ==== | ||
- | |||
- | ==== Another round in the track ==== | ||
- | |||
- | ==== From the track itself ==== | ||
- | |||
- | ==== Manual input ==== | ||