Skip to main content

Interview Status Table

exit_statusWhat It RepresentsDetails About the Blob FilePractitioner_SummaryPatient_Summary
END_COMPLETEDThe patient has completed the interview.- completion_percentage = 100%
- The blob is saved.
- Indicates the interview was fully completed.
On DATE, a GENDER patient named PATIENT NAME presents...You’ve completed the interview! All your answers have been recorded. If you need to revisit any details, just let your healthcare provider know.
END_ABANDONEDThe patient ended the interview abruptly before finishing.- completion_percentage = 0%: The patient abandoned at the very start; the blob is saved (tracks early abandonment).
- completion_percentage < 100%: The patient abandoned partway; the blob is saved (captures partial progress).
The patient chose not to complete the questionnaire and abandoned the chatYou ended the interview before finishing. We have saved your partial answers in case you want to continue later.
END_CONNECTION_CLOSEDThe connection was closed (e.g., patient closed tab, refreshed, lost internet, or timed out).- completion_percentage = 0%: No progress; the blob is not saved.
- completion_percentage < 100%: The blob is saved (captures partial progress).
- completion_percentage = 100%: The blob is saved (core questions answered).
The patient's chat is incomplete and was closed unexpectedly.Your session ended due to closing the tab, refreshing, or losing connection. If you had made progress, we saved it. You can continue where you left off by reopening the chat.

Additional Implementation Details

  • Interview Progress (completion_percentage):
    Indicates how far along the patient got before ending or completing the session.

  • Saved Blob Behavior:
    Determines whether the session data is saved or discarded based on the combination of exit_status and completion_percentage.

  • Multiple Connections:
    All open tabs for the same user share the same session. The last tab to close writes the final blob.

  • Disconnection Handling:

    • Short disconnection: The user can typically pick up right where they left off.
    • Long disconnection / tab closure: The session ends, and the saved blob allows resumption (unless completion_percentage = 0% for certain statuses).
  • Front-End History Limitation:
    Currently, previous messages are not reloaded in the UI upon reconnection (though they remain stored in the blob).