Appointments and check-in
Request or manage appointments, complete forms, and see the destination system acknowledge each supported action.
Krasyn Patient Portal · Private design-partner pilot
A Better Patient Portal Without Replacing Your EMR
Give patients a calm, clinic-branded place for the workflows your connected system can support. Krasyn shows where clinical data came from, when it last synchronized, and whether a patient action is pending, accepted, or needs help.
Availability boundary
Krasyn is accepting design-partner conversations. External-EMR support is validated one connector and one capability at a time. We do not claim a universal connection, and a clinic does not invite patients until its exact capability matrix has passed production validation.
The patient sees what is true now
The portal does not turn a vendor name into a feature promise. It renders only the capabilities validated for that clinic and explains delayed or unavailable states plainly.
Results and records
Review supported results, medications, conditions, allergies, immunizations, visit summaries, and documents with source and freshness shown.
Messages and refills
Send a message or refill request through the clinic-defined route, with a durable pending, accepted, or failed state.
Billing and payments
View supported statements and balances, make payments through the validated payment path, and keep receipts.
Family and proxy access
Use scoped, revocable access for a child, dependent, caregiver, or authorized representative.
Accessible on any device
Core journeys work in a mobile browser. An app install is optional, not a condition of access.
For clinic teams
No hidden integration state
Staff can see connection health and resolve mismatches without asking a patient to repeat an action. Unknown delivery never masquerades as success, and a retry cannot create a duplicate submission.
- Clinic branding, contacts, policies, and patient-facing language from one authoritative configuration
- A capability matrix showing exactly what each connected system can read, request, or write
- Connector health, freshness, delivery, and reconciliation views for staff
- Identity matching and proxy-grant workflows that remain deterministic and auditable
- Message routing, expected response times, emergency boundaries, and notification preferences
- Export, connector disablement, patient access revocation, and customer offboarding
How a clinic connection becomes patient-ready
- 1
Scope
Agree on the exact patient workflows, source systems, owners, and downtime path.
- 2
Connect
Authorize least-privilege access and map versioned data and action contracts.
- 3
Prove
Run identity, freshness, failure, duplication, accessibility, and production workflow tests.
- 4
Invite
Staff approve the rendered capability matrix before any patient invitation.
Keep the EMR. Improve the Patient Experience.
Tell us which EMR you use and which patient workflows matter. We will respond with a scoped pilot path, not a universal compatibility promise.