MyRxWallet North America CorporationA patient-sovereign health record, built to fail small.
MyRxWallet keeps a patient's medical record encrypted under that patient's own key, sharded across five holders with a 3-of-5 threshold, and joined to a consent ledger that records grant, refusal and revocation as events. The company is based in Las Vegas, Nevada, and delivers remotely.
What the company does
- Patient record wallet — the record follows the patient across providers, not the practice.
- Consent evidence — every grant, refusal and revocation is an event with a timestamp and an author.
- Interoperability — FHIR R4 patient access, X12 005010 claims and remittance, CMS-0057-F prior authorization.
- Readiness audit — a two-week, fixed-fee assessment of encryption, consent and interface behaviour, with a written remediation plan.
Technology, in plain terms
| Layer | What is true today |
|---|---|
| Encryption at rest | AES-256-GCM with a per-patient key derived through HKDF; the database stores ciphertext, and reads decrypt only for an authorised request. |
| Sharding | Shamir secret sharing, five shares with a threshold of three: any three reconstruct the key, any two reveal nothing. |
| Consent | A ledger of grant, refusal and revocation, each linked to the record it governs. |
| Interfaces | FHIR R4 with SMART on FHIR for patient access; X12 005010 for claims, eligibility, status and remittance; CMS-0057-F prior authorization. |
| Estate | Self-hosted on AWS; the public estate, its sitemaps and search registrations are managed from the same platform. |
Leadership
The company is led by Olivia Trinh, Chair and CEO. Engineering, compliance and platform operations are coordinated from Las Vegas, with delivery worldwide.
Frequently asked questions
It gives a patient a health record they control: encrypted per patient, sharded across five holders, with a consent ledger that records who was allowed to see what, when, and whether that permission was withdrawn.
A portal shows what an organisation chooses to show. MyRxWallet returns the record the payer or provider actually holds, under a scope the patient granted, and keeps it in a record the patient can move to a new clinician.
Yes. Each patient's record is encrypted under a key derived for that patient; a database copy does not expose plaintext.
The attacker gets ciphertext. Reconstructing a key needs three of five shares, which are not co-located.
Yes — FHIR R4 with SMART on FHIR for patient access, alongside X12 005010 for claims and remittance.
No. Those certifications are not held; the company states that plainly rather than implying otherwise. The security model is documented and the audit service assesses a customer's own posture.
A two-week, fixed-fee engagement at $2,500: encryption at rest, provable consent, and the interoperability gaps that decide how far an incident travels, delivered as written findings and a remediation plan.
Remotely. Scope is confirmed within two business days, fieldwork begins within five, and the report is delivered within fourteen.
Clinics, home-health agencies, pharmacies and small payers that hold patient records and cannot currently prove how they are protected.
Book a 20-minute scope call at myrxwallet.io/scope.html, or pay directly at myrxwallet.io/audit.html.
Contact
MyRxWallet North America Corporation · Las Vegas, Nevada · info@myrxwallet.io · Support