Date: Fri, 29 Mar 2024 05:42:34 +0000 (UTC) Message-ID: <785472928.15.1711690954912@582364e6eb28> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_14_1771061969.1711690954912" ------=_Part_14_1771061969.1711690954912 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There are several treatments or programs that are run by medical organisat= ions that require the patients to adhere to a particular order of visits, t= ests or other checks that are conducted as per a schedule. In such scenario= s, the patient monitoring = flowsheet gives a visual representation of the following:
This flowsheet is driven by a trigger that would define the beginning= of the schedule. For instance, this could be a date like the date of = enrolling the patient into a program or it could be an event, for instance = birth of a child.
The schedule of what needs to be= recorded and when will be defined at a local level by the implementers in = the configuration.
To learn how to configure this feature, please refer to Patient Monitoring Tool in the Implementers Guide.<= /p>
Some examples where this might= be useful are diseases like HIV, TB etc, antenatal and postnatal programs = or immunisation schedules. This disp= lay is meant for the end users who would want to look at the flowsheet= and determine if the patient=E2=80=99s data is complete as per the schedul= e. These users might be clin= icians, program mangers or data managers.
This feature helps ensure data= quality for a patient in terms of data entry. Further it provides a one sh= ot view of the progress of a patient in a particular treatment schedule or = program.
Below is a screenshot of a flowsheet configured for a treatment schedule of Drug resistant Tube= rculosis (DRTB).
On this Page