Apple Health Records
Prepare eligible labs to make patient-authorized records available in the Health app on iPhone and iPad.
Requires partner eligibility, agreements, Apple onboarding, and integration validation.
BUILT AROUND YOUR LAB
Your lab.
Your brand.
Results that
go further.
Bring your results closer to your patients’ everyday lives. Relluvi helps labs plan a connected, lab-branded experience, from their existing portal to digital health records.
Built to connect with Apple Health Records.
Planned for eligible partners. Apple onboarding and integration validation required.
A partner pilot. Please don’t include patient information in inquiries.
THE CONNECTION, SIMPLIFIED Your brand leads
LYOUR LABPatient portal
A FAMILIAR STARTING POINT
Your results are ready.
Patient-authorized access
CONNECTED HEALTH RECORDS
Still your lab.
Now more connected.
✓ Lab identity stays with the record
+
+
YOUR LAB → PATIENT CHOICE → CONNECTED RESULTSIllustrative workflow
More connection.
The same trusted relationship.
Your brand at the center
Your patient relationship
Support from first conversation
WHERE RESULTS CAN GO
Apple Health Records.
And room to grow.
A shared FHIR foundation, with a distinct path for each destination. Your lab’s identity and patient relationship guide the connection.
Android Health Connect
Explore Medical Records support for FHIR lab observations through a dedicated Android app integration.
Experimental platform API. Requires a native app adapter, patient permissions, and validation. Not implemented.
FHIR-enabled patient apps
Explore connections with compatible patient apps using FHIR and SMART authorization standards.
Each app needs its own scope, identity, and interoperability review. No app integration is currently validated.
These are planned connection paths. Relluvi is a partner pilot tested with synthetic data; no live destination integration is currently validated.
A NATURAL EXTENSION OF YOUR LAB
Better access.
Closer connections.
Your results already make a difference. Make them easier to carry forward, with an integration designed around the experience your patients already trust.
Recognition at
every connection.
Designed for lab-branded patient experiences, with your name, approved visual identity, and organization context carried into the connection.
Your patients.
Your ongoing care.
Add a useful connection to your existing service. The model is built to support your portal and patient relationship, without a competing consumer marketplace.
Less friction.
More usefulness.
Work toward authorized digital result sync using patient-scoped FHIR records. Start with a clear source connection and build toward eligible destinations.
A CLEAR PATH, TOGETHER
The legwork, supported.
The decisions, yours.
One shared plan from discovery to launch review. We prepare the integration work and review materials; your team keeps the approvals that matter.
- 01
Start with your setup
Map your result source, patient portal, identity provider, and goals. Agree on a focused pilot.
A shared integration brief - 02
Make it feel like you
Plan your brand, trusted patient identity, result mappings, and consent experience.
Your reviewed connection design - 03
Test before connecting
Exercise the workflow with synthetic data. Review source accuracy, isolation, and access boundaries.
Evidence your team can review - 04
Launch with intention
Complete operational, privacy, security, and destination requirements before real patient use.
An agreed launch & support plan
Planning for Apple Health Records? We help prepare the technical onboarding path. Connectivity depends on partner eligibility, required agreements, and Apple’s independent onboarding and review.
ONE FAMILIAR WAY IN
LYOUR LAB
Welcome back.
Your health information.
Your familiar sign-in.
Approved identity. Patient-scoped access.
Illustrative federated sign-in
FAMILIAR BY DESIGN
Your login.
Your brand.
A connected experience.
Build around your existing identity provider, with a lab-branded authorization journey and an approved link to the right patient record.
- Federated identity designed around your portal
- Explicit patient authorization and scoped access
- Distinct boundaries for each lab and patient
Live federation requires an approved provider integration. Consent and privacy notices identify service providers where required.
TRUST IS PART OF THE DESIGN
A thoughtful foundation
for sensitive information.
Patient information deserves clear boundaries, clear responsibilities, and evidence before a launch.
Separate by design
The integration starter exercises tenant isolation, patient-scoped access, and source-bound identities using synthetic records.
Permission with purpose
The tested authorization foundation covers consent, narrowed scopes, token rotation, and revocation in a local protocol harness.
Review before real data
Production deployments require agreed safeguards, security and clinical review, operational controls, and applicable BAAs.
ROOM FOR WHAT COMES NEXT
Results come in
many forms.
Your connection can grow.
Start with the source and result types your lab needs. Use explicit mappings, keep source context, and review each expansion before it reaches patients.
Map your starting pointQuantitative results
Values, units, ranges, and collection context
Richer findings
Coded, text, ratio, and component-based results
Reports with history
Provenance, versions, and explicit corrections
Source-specific adapters and clinical mappings require lab review. Specialty results and destination support are assessed individually.
A FEW GOOD QUESTIONS
Let’s make
it clear.
Will patients still see our lab’s brand?
The design centers your approved lab name, brand, patient portal, and organization context. Destination branding is subject to that destination’s rules and review. Required privacy, consent, and service-provider disclosures still apply.
Does Relluvi replace our patient portal?
No. The intended model adds a connection to your existing patient experience and result systems. It does not introduce a competing consumer marketplace. The exact workflow is agreed with your team during the pilot.
What does our team need to do?
Bring a source-system contact, an identity or portal contact, and the people who can approve clinical mappings, brand use, privacy, and commercial terms. Relluvi’s onboarding approach prepares the technical plan and review package so responsibilities are clear from the start.
Can you connect us to Apple Health Records?
Apple Health Records is a planned destination for eligible partners. We can prepare the technical integration and lab-specific onboarding materials. Apple makes its own eligibility, vendor, and organization-listing decisions. No Apple approval, listing, device compatibility, or refresh timing is guaranteed.
Is the platform ready for production patient data?
Relluvi is currently an integration starter and partner pilot, tested with synthetic data. Real patient use requires approved live identity and source integrations, encrypted production infrastructure, clinical validation, operational controls, security review, and applicable agreements. The marketing website is separate from that clinical environment.
How do we explore a pilot?
Email matt@mousetechnologies.com to explore a Relluvi partnership. You can also use the integration planner below to create a short, downloadable discussion checklist from your source and identity choices. Nothing is submitted or saved by the planner. Do not include patient information in any partnership inquiry.
LET’S FIND YOUR STARTING POINT
A small first step.
A more connected lab.
Build a short discussion checklist for your team. Start with what you know; work through the rest together.
No patient data. No submission. Just a useful plan.
Ready for a conversation?Contact the partnership team ↗Please do not include patient information.