Skip to main content

v1.0.0: Initial release

Everything HAVEN Hub does by area.

HAVEN Hub is the volunteer and clinic operations platform for HAVEN Free Clinic. It brings the whole volunteer journey into one place: applying and onboarding, scheduling, compliance and training, everyday clinic operations, recruitment, and administration, with role-based access so everyone sees exactly what they need.

For step-by-step guides to everything below, see the documentation.

Signing in and your home base

  • Sign in with your Yale account through single sign-on; you are matched automatically to your member record. Active members whose contact address is not a Yale one can sign in with a one-time emailed link. If your access has ended, the welcome page tells you so and offers a way to sign out.

  • A personalized home dashboard with a greeting, your next shift, your clearance status, a smart to-do feed, and tiles for every area you can open.

  • Navigation that shows only the areas your role allows, with a dropdown on each area for its own pages and an account menu for My Info, Training, and signing out.

  • Cmd+K command palette search across pages, people, cycles, past applicants, and support requests, scoped to what you can actually open.

  • Notifications delivered in the app (a bell and a Notifications page), as Microsoft Teams messages, and by email, with a configurable channel for each type of alert.

  • Automatic sign-out after 30 minutes of inactivity, with a "Still there?" warning and a one-click Stay signed in.

  • Confirmations and errors appear as brief toast messages rather than banners that push the page around. Destructive actions ask you to confirm before they run, and an action that fails inside a dialog reports the error right where you are working.

  • A loading bar and inline spinners show when the hub is working, including when you page, sort, filter, or switch terms.

  • A support assistant in the bottom-right corner of every page, including the sign-in and application pages. Ask a question in chat and some answers come straight back from your own record; anything needing a person is picked up by IT Support, who turn it into a tracked ticket when it needs one.

  • Light, dark, and system themes with readable contrast throughout, and all times shown in Eastern Time.

Your info and compliance

  • Manage your contact details and department memberships, and tell the clinic you are not volunteering this term, with an optional reason. The people who handle offboarding are alerted straight away.

  • A single "cleared for the term" view that combines HIPAA, training, EHS, and learning, with whatever is still outstanding called out at the top, so you always know what is left to finish.

  • Upload your HIPAA certificate and preview it in the app, and see your status at every stage (compliant, pending verification, expiring, expired, or missing). Your status and the expiry shown beside it come from the same certificate, so an upload waiting on verification does not count until a verifier clears it. Outstanding HIPAA and EHS training link straight out to Workday.

  • Separate reminder streams for HIPAA and for outstanding onboarding requirements, each on its own schedule, plus a weekly clearance digest for directors.

  • A Service record: a dated certificate of your terms, departments, roles, and shifts, suitable for residency and fellowship applications, with an optional shareable verification link and a term-scoped wallet badge for your phone. The badge names your role and department and works while you are on the roster. Adding it to your wallet publishes your shared record page, and the page shows as published right away so you can unpublish it if you would rather not share. The record stays available to you after you leave.

  • Subscribe to your own clinic shifts from Google Calendar, Apple Calendar, or Outlook with a private link you can reset at any time.

  • Claim any language you speak, and licensed-RN status. Each language is assessed by the interpreting department, and only a verified one counts you as a provider for it on the schedule. You see every claim you have made and whether it is awaiting review, confirmed, or not confirmed.

Clinic schedule

  • See your assigned Saturday shifts and keep your availability current with structured clinic-date selection.

  • A full clinic view of every department for a date, with shift roles and med-team tags (triage, walk-in, continuity care, remote).

  • Clinic check-in: on clinic days, check yourself in from your phone when you arrive, with a telehealth path for fully remote shifts and a director override for anyone the location check turns away. Directors can mark people present from the full schedule.

  • Request a shift drop or a swap with a partner, with clear eligibility rules and director approval, routed to the approvers of the term the shift belongs to.

  • A director schedule builder with one toolbar for department, working term, and view (day, grid, or availability), live capacity math, availability badges, conflict warnings, and a clearance banner. The sidebar carries a copyable email list for everyone assigned to the selected clinic date, shadows included, deduplicated and comma separated so it pastes straight into Outlook, Gmail, or Apple Mail.

  • Build next term ahead of time: switch the builder to a term still in planning, then publish each department's schedule when it is ready. Members see nothing until it is published, and their own schedule splits into "Live" and "Next term" while both are in play. Archived terms stay viewable, read-only.

  • A read-only coverage view for the directors who run a clinic day without building the schedule.

  • An attending schedule with a grid and a day builder behind one toolbar, and a term switcher for building ahead. Every Saturday of the term is in view, Saturdays the term does not run are marked closed, and you can set on call across a break week.

  • An attending roster owned by the Faculty Relations Manager, with a specialty and credentials on every entry and a credentialing tracker that follows a new attending from the intro email through the forms, the NPDB check, and approval.

  • Each schedule column is mapped to the department it covers, so your home dashboard, your shift cards, and the weekly reminder email name only the attending covering your own department.

  • Reproductive-health readiness with per-clinic procedure checks, procedures booked edited inline next to the procedure cap warning it drives, and the director on point read from the directors assigned to that day's shifts.

  • A three-tier availability model: application baseline, your own updates, and director overrides.

  • Names on the full schedule and in the schedule builder link through to that person's member profile, so you can see who someone is and whether they are cleared without leaving the schedule. You get a link only for people whose profile you are allowed to open; everyone else stays plain text.

  • Close a clinic day and the whole day stands down, volunteers and attendings alike: no check-in invitation, no weekly shift reminder, and check-in stays closed for that date.

  • Weekly shift reminders emailed to everyone scheduled for the coming Saturday, a check-in link on clinic mornings, and a Monday email to attendings listing the coverage for the coming clinic day.

Applying and onboarding

  • A public application portal with a guided, multi-step wizard, a progress rail, save-and-finish-later drafts, and a status tracker.

  • Any Yale account can sign in and apply, even without an existing member record, and is greeted by name; applicants without a Yale account use a one-time email link. Returning alumni are recognised and told which term they served.

  • Applicants can discard a draft, withdraw a submitted application, or decline an offer from their own status card, with staff able to reopen a withdrawal if it was a mistake.

  • Support for new and returning applicants, department preferences, and eligibility checks.

  • Questions that appear or hide based on earlier answers, and a soft word-count guide on long-answer questions.

  • The availability question offers exactly the term's clinic calendar, so nobody is asked about a Saturday there is no clinic on.

  • Token-based onboarding with details prefilled from the application, agreements signed by drawing or typing a signature, HIPAA upload, and promotion into a full member record. The NetID entered on a contract is matched to any record the hub already holds, so the contract skips details already on file such as an Epic ID.

  • A "Get started" checklist that walks new members through profile, HIPAA, learning, and training before the rest of the hub opens, with assigned courses playable inside the checklist itself.

Recruitment

  • Recruitment cycles for volunteer and director tracks, with a planning, open, closed, and archived lifecycle (including reopen, archive, and un-archive to finish anyone still mid-pipeline), and a persistent tab workspace for every part of a cycle.

  • A configurable builder for the application form, the training quiz, and the onboarding contract, with track-specific default starting templates, conditional questions, word limits, an interactive applicant preview, a contract preview per track and department, and forms that stay editable after a cycle opens.

  • Single-use invite links for a closed cycle. You issue a link from the cycle page, it is shown once, it expires after a set number of days, and it is spent the moment the invited person signs in. Invites can be withdrawn, including after they have been accepted, and applications that arrive through one are marked Invited in the applicant list. An invited applicant can get back to their own application at any time: the link still opens after they have used it, their saved draft offers Continue, they can discard it and start over, and their draft is kept rather than expiring after thirty days.

  • Committee scoring, where reviewers rate each application from 1 to 5 on both tracks, with a keyboard Speed score tool for moving quickly.

  • Volunteer applicants are scored and routed to a best-fit department that decides directly, with a Speed route board that bulk-routes by percentile and keeps a returning applicant away from any department that has already declined them; a Stage column, decision filter, and sortable columns track every applicant across the list.

  • Director-track interviews: panelist assignment, scheduling with meeting links, a personal "My interviews" view, 1-to-5 panel scores, and accept, reject, or waitlist decisions, with guards once an acceptance has been sent.

  • A daily review digest for department directors, a Waitlist page for promoting waitlisted applicants, and staff views of the signatures on a submitted onboarding contract.

  • Onboarding as a single filterable table with bulk Send links, Promote, and Withdraw, shift-click range selection, and expired links that can be refreshed without a fresh acceptance.

  • Recruitment history: ten completed Airtable-era cycles imported as a searchable outcome trail, surfaced automatically on an applicant's page so you can see whether they have applied before.

  • Returning applicants who sat terms out are marked as such during review. The applicant list shows a badge counting the terms they were off, and the application page names the term they last served and the terms that ran without them. It is information only: nothing is filtered, gated, or shown to the applicant.

  • Subcommittee assignment and training setup tied to the cycle, including an optional in-person training date that holds the makeup quiz closed until the day after the live session.

  • Editable, per-cycle applicant emails with preview.

Training and learning

  • Term training completed by live-session attendance (recorded by a director) or by quiz, with a configurable pass mark and attempt limits. Failed attempts show learners which of their own answers were wrong without revealing the answer key, and a retry keeps what they already got right.

  • Self-paced learning courses (SCORM) assigned by department, played inside the hub with progress, score, and resume.

  • Courses can be set to retake each term, so annual refreshers come back for everyone at the start of a new term while previous terms' completions are kept. Members can finish the new term's course as soon as that term is set up, before it becomes the active one.

  • A completion dashboard showing who has finished their assigned courses.

Volunteer management

  • A department compliance roster and a clinic-wide master view, with filtering, sorting, and certificate verification. Both list NetID, email, and phone beneath each name, and master roster search matches an email address as well as a name or NetID.

  • A compliance page for each member that opens with a details card: email, phone, NetID, pronouns, Yale affiliation, class year, departments, licensed-RN status, and verified languages. Directors can open it for active members of the departments they run, while setting a completion date or verifying a certificate stays with the people who manage compliance.

  • A verified badge beside the names of people who are cleared for the active term, on the full schedule, the schedule builder, the support request list, and incident report subjects. There is no matching mark for people who are not cleared, so a missing badge says nothing about someone's status.

  • EHS safety-training tracking with per-department requirements and completion.

  • Weekly HIPAA compliance reminders, and a weekly per-director digest of who is not yet cleared.

  • A Term transition view that sorts the whole current roster into returning, pending a decision, and not returning, with bulk flagging, bulk offboarding, and an email export for the changeover.

  • Build a new term's roster by copying an earlier term's forward, choosing which departments and which roles come over. Anyone offboarded since is left out.

  • Offboarding that removes access and memberships across the clinic in one step, with an audit trail, and that captures each departing member's service record so their certificate survives.

Incident reports and standards

  • Anyone can file a Professional Standards Incident Report about anyone, optionally anonymously, and link the people involved.

  • A leadership review queue that sets outcomes and approves or declines disciplinary strikes, with one strike per person named on the report and each strike pointing back to it.

  • Reviewers can ask the reporter a follow-up question on the report itself. The report shows as awaiting the reporter until they answer, and the reporter can add information at any time, including after the report is closed. The notification email, Teams card, and inbox row say a message is waiting without carrying its text.

  • A per-person strikes ledger with confidentiality safeguards that keep sensitive records away from directors.

  • A strike decision carries notes to the member, which are emailed to them and shown on their My Info page. Reviewer notes on the report stay internal.

  • A reviewer can forward a specific report or strike to an email address they type, with previously used addresses offered as suggestions and an optional note. Every forward is listed on the report or strike it disclosed. Confidential strikes cannot be forwarded, and an anonymous report forwards without naming the reporter.

  • Anyone named in a report is locked out of it. They cannot read, forward, delete, or relink that report or the strike from it, even if they review incidents otherwise.

IT support and Epic access

  • A unified support desk to submit and track IT and access requests, and for the support team to triage, assign, and resolve them. Tickets that reach IT by email also appear here, matched to the active member who sent them by the Yale address on their record.

  • Epic and YNHH access tools that generate the YNHH service-request paperwork and track tickets, with business-day aging and overdue alerts. Link a request to a support ticket by picking from a searchable list of open tickets, and the YNHH service request number goes to the linked ticket when you save it. Modify requests prefill the Epic ID, and the History tab shows the most recent closed tickets.

  • Per-department Epic requirements, set separately for directors and volunteers, that decide who is asked for Epic details during onboarding and who gets an access request raised automatically.

  • Support ticket status stays in step with Intercom in both directions, so a change made in either place shows up in the other. Tickets with no Intercom counterpart keep their status controls in the hub.

  • View-only access to the support queue, for people who need to see where every request stands without assigning, resolving, or raising Epic access requests. A view-only viewer searches across everyone's requests and sees each one's details and status, but not its comment thread or attachments.

  • A one-tap Access Epic shortcut on the dashboard for members who already have an account

Did this answer your question?