Skip to content

Improve ability to report on sibling visits that occurred at parent/child visits #38

@cbeaulaurier

Description

@cbeaulaurier

Background

DCYF has timely questions about the number of sibling visits occurring across the state. The goal is to have better data about sibling visits broadly.

Summary

DCYF wants to consider that a sibling visit has happened even if they were AT a parent/child visitation, but multiple siblings are there. From the child's eye view, that counts as a "sibling visit" though it is NOT of type sibling visit, it's a parent/child visit.

Also, if a child is placed in the same placement, they will be excluded by DCYF because they have the placement data. We don't have placement data to exclude these visits.

Question for CSSAT

Can we look at the data and see whether two+ children attended a visit who are siblings?

Issues / complicating factors:

  • Attendees are not recorded in fine-grained manner. A lot of names may be on a referral, but not all of them are expected to be at all visits. Attendees who were present, not present (expected to be present), not present (not expected to be present)
  • Person IDs of attendees are not currently recorded on visit reports by Sprout app. Attendance table in database tries to match names on visit reports to person IDs on referrals to try to get attendee person IDs. mostly works but not every time.
  • Attendees may not always be in the referral (yet) as they are sometimes approved by email from the DCYF case worker. So they wouldn't have a person ID? The person ID comes from the referral.
    • This may be OK as we are currently only concerned with siblings, who are likely to have person IDs from the referral. (So person ID isn't required but we do want the person ID recorded in the database if we can get it.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions