TL;DR
- Epic Welcome is Epic’s patient self-service check-in app. It runs on iPads, and an organization has to license it and be on Epic’s 2018 version or later.
- At the kiosk, patients confirm the visit, update demographics, guarantor and insurance details, sign forms and pay copays. Health systems publish these steps for their own rollouts.
- Hospitals connect other systems around it: identity checks such as palm-vein or photo matching, document capture into a document management system, and card payments.
- Outside intake and check-in tools work alongside Welcome through Epic’s FHIR APIs (Fast Healthcare Interoperability Resources), such as Appointment, Coverage, QuestionnaireResponse and DocumentReference.
If you run patient access at a hospital that uses Epic, or you’re building an intake, check-in or payment product that has to fit next to it, you’ll hear “Welcome” early in the conversation. This guide covers what the kiosk does, where it sits next to MyChart and the front desk, what hospitals plug into it, and what to settle before a go-live.
What Is Epic Welcome?
Epic Welcome is Epic’s patient-facing check-in app. Epic’s App Store listing says the organization “needs to license Welcome”, must be on “Epic’s 2018 version or greater”, and decides the exact feature set; the app is for iPad and requires iPadOS 18.0 or later (Apple App Store, Epic Welcome, checked October 2026). In a lobby it runs on an iPad, often mounted in a kiosk stand.
What patients do on it is set by each organization. The University of Nebraska Medical Center’s Munroe-Meyer Institute described its rollout in July 2025 (UNMC, July 9, 2025). Patients, or their parents, legal guardians or health care agents, now complete arrival on their own, and the kiosk walks them through:
| Step at the kiosk | How often UNMC asks |
|---|---|
| Review and update demographics and emergency contact | every 90 days |
| Review and update guarantor information | every 30 days |
| Confirm primary care provider | every 30 days |
| Patient photo | once a year |
| Verify the day’s visit details | every visit |
UNMC adds that “any updates made at the kiosk are instantly reflected” in its scheduling system, and that patients can still check in with front desk staff if they prefer. Parkland Health’s Welcome kiosks, opened with its new hospital in 2015, also let returning patients pay balances and copays, view upcoming appointments and the insurance on file, and sign in with their MyChart security question (Parkland Health, August 19, 2015).
Welcome is one of many Epic modules, and it sits at the front of the registration work done in Epic Prelude.
Welcome Kiosk, MyChart Check-In and the Front Desk
Is Epic the same thing as MyChart? No: Epic is the record system, and MyChart is its patient portal. Check-in can happen in three places:
- Before arrival, in MyChart: eCheck-In lets patients update personal information, pay the copay, answer questionnaires, e-sign documents and review medications from a phone or computer (University Health, MyChart eCheck-In, checked October 2026).
- On arrival, at the Welcome kiosk: Patients confirm they’re here and finish whatever is still open. UNMC lets patients “begin the registration at home using MyChart and finish their arrival at the kiosks.”
- At the front desk: Staff handle exceptions: a patient the kiosk can’t find, a coverage problem, a guardian question, or anyone who’d rather talk to a person.
| MyChart eCheck-In | Welcome kiosk | Front desk | |
|---|---|---|---|
| When | days before the visit | on arrival | on arrival |
| Who does it | patient or proxy, at home | patient or proxy, in the lobby | registration staff |
| Typical tasks | demographics, insurance, questionnaires, consents, copay | arrival, updates, photo, signatures, copay | exceptions, new patients, fixes |
| Where the data goes | Epic registration and scheduling | Epic registration and scheduling | Epic registration (Prelude) |
Scheduling itself lives in Epic Cadence, which is why arrival status and appointment changes made at the kiosk matter to it.
Need Better Epic Welcome Kiosk Integration?
What Hospitals Connect to the Kiosk
Around Welcome, hospitals connect other systems, and those vendors publish how their products work with the kiosk.
- Identity: Matching a patient by name and date of birth at a self-service screen is the weak point, and identity vendors document add-ons built for the Epic kiosk. Imprivata’s PatientSecure documentation has an “Epic Kiosk” settings section: patient photo capture during enrollment or authentication, age limits for kiosk enrollment with a default minimum of 7, and idle timeouts that default to 60 seconds (Imprivata PatientSecure 6.12 SP1, updated May 7, 2025). Imprivata’s Patient Access release notes for 2026.3 add that “the Epic Welcome kiosk now accepts 2-digit values for a patient’s birth year” (Imprivata Patient Access release notes, topic updated March 16, 2026). Parkland’s 2015 kiosks shipped with palm-vein readers.
- Documents: Insurance cards, IDs and signed paperwork have to land in the chart. Hyland’s OnBase documentation describes an Epic Welcome integration: “Patients who register using the Epic Welcome software can scan and upload documents directly to OnBase from a kiosk,” and documents are archived to a document type “using the patients’ registration information” (Hyland OnBase Integration for Epic, Foundation 22.1, checked October 2026).
- Payments: Copays and prepayments run through a card reader at the kiosk, and payment can break. Weill Cornell’s IT team posted an incident from August 31 to September 4, 2026: some patients with a copay or prepayment stalled at the payment step, or had to retry several times, before Welcome kiosk payment was re-enabled (Weill Cornell ITS). When payment fails, the patient walks to the desk, which is the queue the kiosk was meant to shorten.
- Hardware: The app runs on iPads; around it sit enclosures, card readers, signature pads and scanners, plus accessibility features (Parkland’s 2015 kiosks were wheelchair accessible and adjustable).
Welcome’s own configuration sits with the hospital’s Epic team.
Building a Check-In or Intake Tool Alongside Welcome
Many digital-health products do intake work that touches the same moments: pre-visit questionnaires, insurance capture, consent, payment estimates or specialty intake forms. They sit beside Welcome, reading and writing through Epic’s APIs, and the hospital decides which of them to switch on.
Why would a hospital that already licenses Welcome and MyChart turn on another tool? A tool earns its place when it brings something Welcome’s standard steps don’t carry: a specialty intake questionnaire, a clinical screening the care team needs before the visit, or a digital-health product’s own pre-visit flow that the patient already uses. Check-in itself still belongs to Welcome or the desk. Epic’s capability statement lists Appointment as read and search only, so an outside app can find the visit but shouldn’t plan to mark the patient arrived; check Epic’s API catalog for any arrival or booking operations before designing around it.
Epic’s FHIR R4 capability statement (sandbox metadata, August 2026 release, checked October 2026) lists these resources for the jobs an intake tool does:
| Job in your tool | FHIR resource | Listed interactions |
|---|---|---|
| Find today’s visit | Appointment | read, search |
| Match or register the patient | Patient | read, search, create |
| Check insurance on file | Coverage | read, search |
| Ask intake questions | Questionnaire / QuestionnaireResponse | read, search / create, read, search |
| Save a form or scanned document | DocumentReference | create, read, search, update |
| Read recorded consents | Consent | read, search |
A capability statement describes what the server supports. Your app’s access is set in its Epic app registration and switched on by each health system, and Epic’s own API catalog lists the details for each API; our Epic FHIR API guide walks through them. The first thing I check when scoping an intake tool against Epic is the gap between those two lists. If your tool also launches inside Epic for staff, see SMART on FHIR launch for Epic. For scheduling depth, see our Epic scheduling API guide. Insurance checks often go to the payer directly: an X12 270/271 eligibility request, the standard electronic eligibility exchange, returns coverage and benefit details before the patient arrives.
We built the Epic integration for a financial-assistance technology company that pulls patient data from Epic through HL7 and FHIR, cutting its manual data entry by 90%. Intake tools aim at the same thing: capture patient data once and stop retyping it.
There are two ways to work with us:
- Mindbowser builds it: We build intake, check-in and patient-access apps that work alongside Epic, using FHIR and HL7, and we help you through Epic’s app registration, which Epic makes self-service; each health system decides whether to activate your app. See our Epic integration work, and our Epic Showroom guide if you plan to list the app.
- You run ConnectHealth: ConnectHealth is our EHR integration product: HL7 v2, FHIR and X12 in, one consistent format out (REST, FHIR or webhook), with real-time eligibility (X12 270/271) via Stedi. ConnectHealth doesn’t remove vendor registration or the hospital’s approval chain.
For the patient-facing side beyond check-in, see our digital front door work.
What to Settle Before a Kiosk Go-Live
Published outcome evidence on kiosks is limited. A 2025 systematic review of check-in and triage kiosks in emergency departments found only five studies (47,778 patients); one reported 97% uptake, while effects on waiting times were mixed (Lammila-Escalera et al., J Med Internet Res, 2025). These are the points to settle first:
- When the kiosk can’t find the patient (owner: patient access, with the Epic analysts): Decide what happens on a failed match: send the patient to the desk, or let them register as new. A loose rule creates duplicate records someone has to merge later.
- Payments and PCI scope (owner: revenue cycle, with IT security): Who processes the card, how the reader is certified, and what the patient sees when a payment fails. PCI DSS (the card industry’s data security standard) applies to whatever touches the card.
- Which forms are signed at the kiosk (owner: compliance, with patient access): List each consent and form, its version, and where the signed copy lands: in Epic or in your document system.
- Accessibility and a staffed fallback (owner: patient access and facilities): Screen height and reach, language options, proxies such as parents and guardians, and a person nearby for anyone who needs one.
- How updates reach scheduling and registration (owner: Epic analysts, with the interface team for any outside tool): UNMC reports kiosk updates are “instantly reflected” in scheduling. Test that end to end, including anything your own check-in tool writes back.
- What happens before arrival (owner: patient access, with the MyChart team): Decide which tasks move to MyChart eCheck-In, so the kiosk is a quick confirmation instead of a long form in a busy lobby.
The health systems above already offer demographics, insurance, forms and copays in MyChart before arrival, and use the kiosk to confirm arrival and catch what’s missing. Plan your intake around that split, and the kiosk becomes a quick last step.
Next read
- Epic Prelude: how registration works behind the kiosk.
- Epic Grand Central: what happens to a patient after check-in, from bed to discharge.
- Epic scheduling API guide: booking and appointment data for outside apps.
Where to go next
- Have us build it: Epic integration
- Run it yourself: ConnectHealth
- Patient experience: Digital front door
- Talk to us: Start a Conversation








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 


















