Skip to main content

How does visitStartedHoursAgo measure the the visit length?

Updated

Question:

In the rules-based notification yaml file, how does visitStartedHoursAgo measure the the visit length? Am I measuring their most recent active encounter or does it measure across their ED and inpatient visit?

visitStartedHoursAgo = ED LOS + Inpatient LOS?

id: _smsServiceRequest1
type: patient-sms
relation: gold.service_request_1
content:default: 
    'Our goal is to provide you with the highest level of service. If you are in pain, cold, thirsty or need something else to make you comfortable, please make a request at {patientInviteWithServiceRequestRedirect}'visitStartedHoursAgo:24enabled:true

 

 

Answer:

visitStartedHoursAgois the maximum time since the visit started (the earliest of the emergency start time and the inpatient start time) that we are able to send messages from this rule. This is generally a final safety fallback that we have in Conductor to catch bad data rather than actual logic for when we send the message.

For the example above, we won't send the_smsServiceRequest1message to a patient whose visit started more than 24 hours ago. However, the actual logic for this rule is as follows:

  1. The emergency visit has started

  2. The patient is not in an inpatient location

  3. The patient does not have an outcome (i.e. is not discharged or admitted)

  4. It is between 15 and 30 minutes since the visit started.

  5. the patient is in a location with active* service requests

*active: there is a clinician online and available to respond to the request.