...
- create a person.
- make person become a patient.
*person --> patient
*needs identifier and location
*each identifier needs to be unique in "space and time".
-sencha doesn't yet provide this directly. But we need this. **should figure a way to get unique identifier for a device
-hlocation is tied to a different device. this means that each patient will be unique. - each patient is going to have an associated "registration encounter". each patient can have another encounter type called "screener encounter"
(we may be concerned that a screener should be able to request a flexible, variable set of observations (blood pressure, etc))
REST call: /patientlist/uuid <= here is the unique identifier for the patientlist type. one patientlist for registration, one for screener, one for doctor encounters
name: screenerList (or registrationList, doctorList, etc)
desc: Patients who have registration encounters today (or whichever date) but no screener encounter
searchQuery: ?encounterType:=registration &&startDate: =.... &&endDate: =.....&& inlist inList=<uuid for registration list>&& notinlist: notInList=<uuid for screener list>
--> to find the 'unscreened patients', we need to find everyone who is in the registration list, but not in the screener list (they have a registration encounter but no screener encounter)
What should we return? The simplest solution is to return a list of patient resources.
But this means to find the observations we need to screen (such as BMI) we would have to do GET calls for each patient, total of possibly 100 GET calls just for screener list to load
Instead, the Query should return not only a list of patients, but also all the observations linked to those patients and that encounterType
--> for example, say a registration encounter recorded height and weight, we would return height and weight from the Query
...