fct_observations

Unique ID of the observation. E.g.: 5396.

ID of the member associated with the visit. E.g.: 2019.

Profile ID of the staffer subject to verification. E.g.: 10.

ID of the membership associated with the visit. E.g.: 1989.

Unique ID of the community to which the helper belongs. E.g.: 123.

Name of the community associated with the helper. E.g.: Adelaide West.

Timestamp when the observation was raised, originally the created_at date. E.g.: 2021-05-02 00:10:57.

Categories assigned to the observation by Lookout, which could include one or more of the following: “cognition”, “emergency”, “external_communication”, “fall”, “illness”, “medication”, “negative_mood”, “risk”, “wound”, “survey”. E.g.: ‘emergency’, ‘fall’.

Current state of the observation, which can be one of ‘investigated’, ‘uninvestigated’, ‘discarded’.

Timestamp when the observation was assessed by a staffer. E.g.: 2021-05-02 00:10:57.

Profile ID of the staffer who completed the assessment. E.g.: 5494.

Number of hours taken to assess the observation. E.g.: 5.

Number of days taken to assess the observation. E.g.: 2.

Risk level identified by the staffer, can be one of ‘low’, ‘medium’, ‘high’. E.g. ‘high’

Numeric value mapping to the risk level, where {‘low’: 1, ‘medium’: 2, ‘high’: 3}. One of 1, 2, 3. E.g.: 3.

List of actions identified by the staffer to be taken post-observation, which can include one or more of the following: “continue_as_planned”, “more_info_auth_rep”, “more_info_helper”, “more_info_member”, “raise_incident”, “refer_health_professional”, “refer_nurse”, “refer_reassessment”, “update_help_plan”. E.g.: ‘more_info_helper’, ‘raise_incident’.

The system entity that raised the observation, which can be one of ‘MembershipNote’, ‘SurveyRequest’, ‘ExternalDeviceAlert’, ‘AutomaticMustDo’, ‘ExternalObservationAlert’, ‘DeviceAlert’, ‘Visit’. Below is a description of the most used sources: - Visits: These are created through the Remote Care Monitoring model based on checkout notes of a visit. If the model deems the note to be worth investigating, an observation is raised. For more information, visit: https://thelookoutway.com/remote-care-monitoring. - AutomaticMustDo: If a visit automatic must_do response was a No, an observation is raised. If it’s Yes but a comment was left, then that comment goes to the same Remote Care Monitoring model to determine the risk. If it’s at risk, an observation is raised. - SurveyRequest: An observation is raised if a response exceeds a certain threshold (e.g., 5 on a 1-5 scale) in a Survey. - MembershipNote: Membership notes are created by Helpers. These notes are then passed through the Remote Care Monitoring model to determine the risk level. If it’s at risk, an observation is raised.

Unique ID for the system entity raising the alert, used in conjunction with source. For instance, if the source is ‘Visit’, this would be the visit_id, e.g., 5943.

State of the visit that led to the observation, which can be one of ‘canceled’, ‘completed’, None.

Indicates if the observation was raised by the Lookout algorithm. One of ‘True’, ‘False’.

Specifies if the observation was raised by the first iteration of the Lookout algorithm. One of ‘True’, ‘False’.

Determines if the observation was raised by the second iteration of the Lookout algorithm. One of ‘True’, ‘False’.

Indicates if the observation was raised by a helper. One of ‘True’, ‘False’.

Indicates if the observation was raised by a care manager. One of ‘True’, ‘False’.

ID of the company. E.g.: 345.