Editing Tupaia (section)

==Configuration==

Data capture and reporting for this programme has been rather a PITA, to be quite honest. The current model is as follows:
* Needs assessment is initially done by Whanau Ora navigators using an MS Forms form.
* A Flows flow simply emails the text of this assessment back to the submitter.
* This flow also adds some 'codes' to the form, depending on question responses. This component is intended to flag needs which can be picked out from note data once entered into Indici (see below).
* The email response can then be copy-pasted into one of the bazillion systems that Whanau Ora is required to use. Specifically, in this case:
** [[Indici]]
** Penelope - the Whanau Ora CMS forced upon us by the funder
** Aiga - K'aute's current in-house CMS.
* The codes are subsequently pulled out of <code>QuickConsult</code> data when it comes through overnight. Postgres function <code>rpt.fn_tupaia()</code> executes the following steps:
** Pulls out the client details of anyone having QuickConsult data containing specified keywords indicating an assessment has been completed
** Cohort is separated by children (18yrs and under) and adults
** Subsequently codes for all the above 5 pathways are searched in turn
** Summary data is then written to <code>rpt.tupaia_overview</code>.

This will present a table of unique individuals with a range of columns flagging which codes have been assigned to them.

Note that codes are always assigned manually (even from the initial assessment, code assignment is based on question response). The current list of codes and meaning is:

{| class="wikitable sortable"
! Pathway || Code || Description
|-
| Long term conditions || LTC1 || LTC need is identified
|-
| Long term conditions || LTC2 || Follow-up with GP booked
|-
| Long term conditions || LTC3 || LTC needs dealt with by GP
|-
| Long term conditions || LTC4 || Patient will follow up with their own GP
|-
| Eye || EYE1 || Eye needs identified
|-
| Eye || EYE2 || Clinic follow-up is booked
|-
| Eye || EYE3 || Eye needs have been treated
|-
| Eye || EYE4 || Decline/NA
|-
| Dental || DEN1 || Dental needs identified
|-
| Dental || DEN2 || Dental appointment booked
|-
| Dental || DEN3 || Dental treatment completed
|-
| Dental || DEN4 || Decline/NA
|-
| Surgical || SUR1 || Surgery need identified
|-
| Surgical || SUR2 || Surgery is booked
|-
| Surgical || SUR3 || Surgery has been completed
|-
| Surgical || SUR4 || On public waitlist
|-
| Mental health || MH1 || Mental health needs identified
|-
| Mental health || MH2 || Appointment with psychologist booked
|-
| Mental health || MH3 || Mental health treatment plan completed
|-
| Mental health || MH4 || Mental health support is declined
|}

Finally, a reporting summary is prepared using view <code>rpt.vw_tupaia</code>. Currently this is used as the sole data source for overview/detail reporting into [[Power BI]].