Verify Logic to Identify CVT Appointments with VAOS

[loripusey]

Description

We need to verify the logic that Shawn Adams identified for us for how CVT appointments are managed in other VA applications.

Tasks

• Meet with VAOS to verify the logic
  • Q for VAOS: how are you visually displaying the Patient's appointment? And, was there Veteran research completed as part of this?
  • Agree on how we want to handle CVT appointments in Pre-Check-in and Check-in
  • Make sure we invite an engineer from CIE and an engineering from CHIP

Logic to Identify a CVT Appointment

• Are there 2 appts for same patient on same day that are 0-5 minutes apart?
  • Yes
    • Does one of the 2 appts have a telehealth stop code?
      • Yes
        • These 2 appts are part of a CVT appt
      • No
        • Stop
  • No
    • Stop

How We Will Want to Treat a CVT Appointment

• Display the one that DOES NOT have the telehealth stop code to the Veteran in Pre-Check-in and Check-in
• When Veteran checks-in for their in-person appointment that is part of a CVT appointment, we also want to complete check-in for the doctor-side appt

[kristenmcconnell]

@kristenmcconnell To coordinate the meeting invite with VAOS, CHIP, and Check-in.

[kristenmcconnell]

Message sent to Jeff Roof and Chris Horton to identify CHIP and VAOS team members, who should join the meeting.

[kristenmcconnell]

Put a meeting on the calendar for August 2 from 3 - 3:30. I'm adding @acrollet and @randomsync to this ticket, so they can help document any findings from the meeting.

[benbrasso-agile6]

@kristenmcconnell and @benbrasso-agile6 (or other UXers) should sync up with VAOS team who is just about to run a study on displaying different modality types and names. Peter and team are also working with Danielle and team on naming of the modalities.

We should reach out and see how we can collaborate.

Right now, they're using a structure of modality type at location/facility. Could be worth testing the opposite. E.g., location/facility with modality type.

[acrollet]

The VAOS team was not aware of the CVT appointment modality and wasn't sure how they are displayed. I've reached out to try and get access to the MAS source to see what the logic is for detecting CVT appointments and how they are categorized, which should give us a better idea of how they are displayed in VAOS.

[loripusey]

@acrollet do you need a f/u ticket for this? @loripusey

[acrollet]

@loripusey IMO we just need to keep this ticket open, I don't consider it resolved yet.

[loripusey]

Meeting with VAOS on 8/10/22:

• CIE wants to learn about CVT appointments, how VAOS identifies them and how they are displayed to end users, we want to mirror what VAOS does
• How does VAOS identify telehealth appointments
  • Has an associated Clinic that is a telehealth clinic (i.e. has a stop code that belongs to a list maintained internally)
  • Is a video appt in Vista
• I explained our logic given to us by Shawn Adams to them and they agreed it sounds right
• Brad Crosby's team
  • MAS v1 is read only
  • VAOS service - has write ability
  • MAS v2 (accesses new VAOS service)
• EAS is same team
  • Long-term where we are heading
  • Will replace all of these services
  • Building right now but does not exist
  • Is there a sand box? No
  • Are there docs? No
  • Will be fire(sp?) compliance
  • No test env yet
• We should reach around mid November about EAS
• Mentioned that we should only return the appointment relevant for the patient (patient vs. provider stop codes???)
• Is there VAOS service documentation? Have some Swagger docs in Atlassian
• Talked about us potentially providing access to check-in link to VAOS in the future

[acrollet]

This is on hold until we have access to the MAS source to verify the logic.

[acrollet]

MAS takes a simple approach and uses the appointment start time to group appointments - if two appointments start within a configurable threshold, (defaults to 5 minutes but may be set to as much as 10 minutes in production) they are grouped as a single logical appointment.

References:

• internal appointment ID mapping docs: https://coderepo.mobilehealth.va.gov/projects/EAS/repos/mobile-appointment-service/browse/docs/logical-id-mapping.md
• appointment mapping code: https://coderepo.mobilehealth.va.gov/projects/EAS/repos/mobile-appointment-service/browse/mobile-appointment-service/src/main/java/gov/va/mobile/appointment/v2/utils/MergeAppointmentUtils.java

[acrollet]

MAS merges appointment data to create a logical single appointment as mentioned above. Ultimately VAOS doesn't have to check appointments in, so I don't think they're as concerned with the distinction between the patient-side and provider-side appointments as we are. When we revisit this topic we should ask Shawn for a sampling of CVT appointments so that we can verify our logic for determining the provider and patient side. Ultimately we'll want CHIP to have the same concept of a logical appointment, so that we can deal with a single appointment on the vet-facing side and have CHIP take care of handling the check-in correctly. (That is if we haven't moved to using EAS in the meantime)

[loripusey]

Here are the notes from our meeting with Shawn; the logic and functionality we proposed for eCheck-in based on the info from that meeting was the following. Does this make sense now based on what you have discovered @acrollet?:

• If there are 2 appts for same patient on same day that are 0-5 minutes apart (probably 95%) (VAOS & My Healthy Vet)
  • Don't display the one that has a telehealth stop code
  • Do display the one that DOES NOT have a telehealth stop code
  • When check-in then do check-in for both of the appointments

[acrollet]

@loripusey that makes sense based on what I've seen, however there's nuance in that I think we'd have to pull the provider name from the non-telehealth appointment.

[loripusey]

Sounds good, I mainly just wanted to get our thoughts down so when we pick this back up we will have a path forward.