“Patients should own their health data the way they own their homes — with a deed, a lock, and a key only they control. That is not a feature. That is the architecture.”
— Olivia Trinh, Chairman & CEO
April 17, 2026 · inferno.healthit.gov · Public Federal Record
A National Infrastructure Milestone
On April 17, 2026, MyRxWallet achieved a full pass of the ONC Inferno v8.0.0 test suite — all 317 sub-tests. This is the same federal standardized API test suite required of every ONC (g)(10) Inferno-tested EHR in the United States.
317/ 317 Sub-Tests Passed
0Failures
1stAttempt
Verifiable at inferno.healthit.gov · Led by Olivia Trinh and a small founding team · Built on infrastructure the company owns outright · Bootstrapped — no institutional venture capital raised.
Patients should own their health data the way they own their homes — with a deed, a lock, and a key only they control. That is not a feature. That is the architecture.
4 sovereign channels · Owned outright · Not AWS · Not Azure · Not Ethereum. Every node. Every channel. Every audit trail. Infrastructure the company controls completely.
Designed to direct 85% of data royalties to patients via on-chain MRT closed-loop loyalty rewards. On-chain enforcement architecture designed. Currently in development-stage deployment. [Per SEC Comment 13 framework — not a security]
Patient Loyalty Rewards Program — Development Stage
Your health data has been making other people rich for 40 years. We’re designed to pay you for yours.
MyRxWallet’s RoyaltyDistributor smart contract is designed to direct 85% of data royalties to patients via on-chain MRT closed-loop loyalty rewards. Currently in development-stage deployment on MYRX-MAINNET (Chain ID 8472). Not yet operational.
DEVELOPMENT_SEED_DATA · In design phase · Not yet operational · Subject to change · Not investment advice · [Per SEC Comment 13 — closed-loop loyalty rewards, not a security]
● DEA EPCS — 21 CFR Part 1311 aligned, audit in progress
Infrastructure Status — Live
✅MYRX Mainnet Live — Chain 8472
✅10,000,000,000 MRT Token Treasury Funded
✅L4 Hyperledger Fabric Testnet Live
✅EHIgnite Phase 1 Submitted
✅Patient Enrollment Opening
“MyRxWallet North America Corporation’s sovereign blockchain infrastructure is live. Members who enroll today will be among the first to receive MRT rewards when the earning loop activates.”
Patient Portal
Your sovereign health dashboard — ONC (g)(10) Inferno-tested API, HIPAA-aligned architecture, AI-assisted.
🏥
Patient Portal
patients.myrxwallet.io · Full sovereign health record access
MyRx Credential issued on enrollment — soulbound identity attestation
Full medical record ownership and portability via FHIR R4
AI health coach — MyRx-Assistant + MyRx-HealthCoach (informational use only; see Clinical AI Disclosure)
Consent control — one tap to grant or revoke provider access
Emergency card with instant provider QR/NFC access
Prescriptions, labs, vitals, immunizations — all in one vault
HIPAA compliant · AES-256-GCM encrypted · Zero PII on-chain
The organization behind a patient-controlled health identity platform.
Our Mission
MyRxWallet North America Corporation exists to put patients in absolute control of their health identity — permanently. We build infrastructure in which patient data control remains with the patient. No third party outside MyRxWallet can revoke or transfer a patient's credential. MyRxWallet retains revocation authority only for off-boarding, consent withdrawal, or security incidents, and each revocation is logged on-ledger.
Our Foundation
Led by Olivia Trinh, Chairman and CEO
Incorporated in Wyoming, USA
CAGE: 9VNZ7 · NAICS 518210 · SIC 7374-00
Unique Entity ID: MVKQW9DKKGB8
Our Values
Patients first — always
Zero data brokering — patient data is never sold
Open standards, fully interoperable
Zero Dependency infrastructure
Built on open standards; patient data is never sold
About Us
The story, the conviction, and the infrastructure that defines MyRxWallet.
The Founding Story
MyRxWallet was born from a simple but radical conviction: your health data belongs to you — not your insurer, not your pharmacy chain, not your EHR vendor. We built the infrastructure to make that a legal reality, not a marketing promise.
Why We Exist
Over 12M Americans lack a consistent health record
$350B+ lost annually to fragmented, siloed data
Most patients cannot access or control their own records
Existing platforms monetize data — we don't
Our Credentials
Headquartered: Las Vegas, Nevada
ONC-registered developer — 10 SMART client IDs
USCDI v7 submission #703 — on federal record
NPI registered — multiple provider identifiers
Electronic prescribing architecture aligned with 21 CFR Part 1311 (third-party audit in progress) — electronic prescribing
What We Offer
A complete sovereign health ecosystem — purpose-built for patients, providers, and institutional partners.
For Patients
Sovereign health identity — MyRx Credential
Full medical record ownership and portability
AI health coach and clinical decision support
Emergency card with instant provider access
Platform activity tracking for clinical workflow purposes only
For Providers
ONC (g)(10) standardized API test — PASS with FHIR R4 — live
EPCS electronic prescribing — 21 CFR Part 1311 aligned; third-party audit in progress
Telehealth + scheduling built in
SMART on FHIR payer client architecture (CMS Blue Button live; commercial agreements in progress)
Hyperledger consent trail — HIPAA-grade audit
For Partners
White-label EHR infrastructure — licensing available
MyRx Credential issuance integration
Developer API + SMART on FHIR
Pharmaceutical and insurance API integrations
Our Technology Stack
Enterprise-grade infrastructure built from the ground up for health sovereignty and regulatory compliance.
Backend & API Layer
FastAPI (Python) — EHR core backend
FHIR R4 — full interoperability compliance
PostgreSQL — encrypted, sovereign health records
SMART on FHIR — OAuth2 + PKCE authorization
ONC (g)(10) Inferno test suite — PASS (317/317), April 17, 2026
MyRx-Sentinel v2.0 — DoD STIG hardening standards applied
WireGuard VPN — MyRx-Gateway zero-trust overlay
Credential-keyed service access — port-level auth
Zero Trust architecture — no implicit trust
Sovereign VPS — all data stays on our metal
Identity Credential
The MyRx Credential — a soulbound health identity credential. Non-transferable by design. Not a tradable asset.
Utility Credential Notice
The MyRx Credential is a non-transferable, soulbound access credential — not an investment product, financial instrument, or security. It has no market value, cannot be bought or sold, and confers no expectation of profit. It functions solely as a platform access key, identity attestation, and consent record on a permissioned ledger.
What Is the MyRx Credential?
Each MyRxWallet member receives a unique, non-transferable credential issued on our permissioned Hyperledger Fabric network. It is their sovereign health identity attestation — proving who they are, controlling what they access, and recording consent history permanently on-chain.
Credential Functions
Identity attestation — cryptographic proof of identity
Platform access key — gates services by authorization level
Consent ledger — immutable HIPAA consent record on-chain
Participation record — tracks health-positive platform activity
Credential issuance — providers can onboard patients directly
Non-custodial — only the holder controls their credential
SDK: @myrxwallet/credential-sdk on npm
Governance Framework
Advisory governance structure — eliminating single-point control over health infrastructure.
Corporate Governance Clarification
MyRxWallet North America Corporation is governed by its Board of Directors and Officers under Wyoming corporate law. Advisory input from credentialed participants on protocol and technical matters is non-binding and confers no voting rights on Company matters, no equity, no profit participation, and no security of any kind.
What Is the MyRx DAO?
The MyRxWallet DAO is a decentralized governance structure that guides platform evolution. Credentialed participants contribute governance input on protocol upgrades, fee structures, and partner integrations — removing unilateral control by any single entity.
DAO Functions
Protocol governance — proposals and votes on upgrades
Fee schedule — community-reviewed rate structures
Operational allocation — voted by governance participants
Partner vetting — on-chain approval process
Incident response — on-chain audit log
Why Zero Dependency?
No single institution can freeze the platform
No vendor lock-in at any infrastructure layer
Protocol changes require community consensus
Patients always retain control of their own data
Open governance — auditable by design
Staking & Validators
Chain 8472 validator network — securing federally mandated patient health infrastructure. MRT token compensation model, NFT-gated credentialing, and DAO governance. Regulatory framework published proactively.
Regulatory Disclosure
MRT tokens are infrastructure compensation instruments — not investment securities. Validators perform active computational work securing patient health data pursuant to the 21st Century Cures Act. This position is documented in our publicly available Regulatory Framework White Paper. Nothing here constitutes an offer of securities.
⛓️ What Is Chain 8472?
Chain 8472 is MyRxWallet's custom Ethereum-compatible blockchain (EVM, Chain ID 8472) purpose-built to secure, transmit, and make interoperable patient health data under the 21st Century Cures Act, HIPAA, and the ONC Interoperability Rule.
RPC: rpc.myrxwallet.io
Full EVM compatibility — deploy any Solidity contract
2-second target block time
Native token: MRT (MyRxWallet Reward Token)
Developer SDK: npm install @myrx-token/sdk
🌐 5 Chains Live — Multi-Chain Bridge
MRTBridgeMint contracts deployed and live across all 5 connected EVM networks. Multi-protocol bridge: Across, Hop, Stargate, deBridge.
Validators are active infrastructure operators — not passive investors. They perform real computational work that directly fulfills federal healthcare law.
Block validation — confirms patient data hash integrity
Consensus participation — distributed agreement, no single point of control
Audit trail maintenance — HIPAA §164.312(b) compliance at consensus layer
Node uptime — 99%+ availability for uninterrupted patient data access
MyRxWallet NFTs function as the blockchain-native equivalent of a HIPAA Business Associate Agreement (BAA) — a digital credential that gates validator access.
Tier 1 — Founding Member: Full validator rights + enhanced MRT multiplier
Tier 3 — Community NFT: Standard validator rights + DAO governance
Developer NFT: Validator rights + SDK access grants
🏗️ MRT Token — Infrastructure Compensation
MRT rewards are service compensation for active infrastructure work — not passive investment yield. The distinction is legally significant under the Howey Test.
Validator bond — slashable stake to participate in consensus
Network gas — Chain 8472 transaction fees denominated in MRT
4 Go chaincodes — CaaS deployment, sequence 2 VALID
myrxchain Docker network — fully isolated
The 4 Channels
Identity channel — identity credential ledger
Consent channel — HIPAA consent audit trail
Health channel — encrypted health event log
Participation channel — platform activity ledger
Why Hyperledger?
Permissioned — only authorized nodes participate
HIPAA-grade audit trail built into the protocol
No public blockchain exposure of health information
Go chaincode — enterprise throughput
Linux Foundation — open standard, no vendor lock-in
Our Rail
MyRx-Rail — the sovereign health data transport layer connecting every node without third-party cloud dependency.
What Is MyRx-Rail?
MyRx-Rail is our proprietary health data transport infrastructure — combining FHIR R4 APIs, Hyperledger channels, and WireGuard tunnels into a unified sovereign rail that moves health records without ever touching a third-party cloud provider.
Rail Components
FHIR R4 API — inbound and outbound data exchange
MyRx-Gateway — WireGuard VPN zero-trust overlay
Hyperledger channels — immutable on-chain event bus
CMS Blue Button 2.0 connector — live; commercial payer connectors under discussion
Rail Standards
TEFCA / QHIN — national health information interoperability
USCDI v7 — all universal data classes supported
SMART on FHIR — app authorization and launch protocol
CDS Hooks — clinical decision support at point of care
Bulk FHIR — population-level export for research
Why Partner With Us
A sovereign health identity platform built on ONC (g)(10) Inferno-tested infrastructure, Hyperledger blockchain, and a federally-aligned regulatory architecture.
Unmatched Regulatory Standing
ONC (g)(10) standardized API test — PASS API (g)(10) — production ready
EPCS prescribing — 21 CFR Part 1311 aligned; third-party audit in progress
Hyperledger consent trail — legally defensible audit record
DoD STIG hardening standards applied — highest achievable security posture
USCDI v7 submission #703 — on federal record
Commercial Opportunities
White-label EHR licensing — subscription and per-seat models
API access — per-call and enterprise subscription tiers
Pharmaceutical integration — formulary and prior auth APIs
Insurance integration — eligibility and claims pipeline
Strategic Position
USCDI v7 Comment #703 filed with ONC (April 11, 2026); FDA CDER concept paper submitted (no regulatory response received)
Architecture aligned to HSCC CWG published guidance (no formalized HSCC CWG partnership)
Global partnerships framework — live and operational
Zero data brokering — patient data is never sold
Platform Access Program
Service-based compensation for providers and partners. Engagement recognition for patients.
Program Disclosure
All compensation described here is paid for verified service delivery — not for holding, purchasing, or speculating on any credential or digital asset. MyRx Credentials have no market value. Participation programs are governed by signed service agreements.
How the Program Works
MyRxWallet operates structured service-fee and engagement-recognition programs. Providers receive compensation for verified clinical services. Patients receive recognition for health-positive behaviors — similar to established wellness incentive programs in the insurance industry.
Provider Service Compensation
Credential issuance fee — for onboarding new patients
Per-session fee — verified telehealth completions
EPCS service fee — verified electronic prescriptions
All governed by platform service agreement
Patient Program Features (No Monetary Value)
Profile completion progress indicators
Medication adherence reminders — tracked via MyRx-MedTracker for clinical workflow purposes only
Preventive care appointment reminders
Anonymized research consent — patient-controlled, opt-in only
All program features are administrative in nature — no monetary value, no redemption, no exchange for cash or any item of value
Our Roadmap
Where we've been, where we are, and where we're going — all infrastructure, no vaporware.
✅ Complete (Phase 1–4)
ONC (g)(10) Inferno test suite — PASS (April 17, 2026, 317/317) + FHIR R4 API — live
Patient + Provider portals — live
MyRx-Chain — Hyperledger Fabric 2.5 LTS
MyRx-Sentinel v2.0 — DoD STIG hardening standards applied
USCDI v7 #703 — filed April 11, 2026
Credential SDK — @myrxwallet/credential-sdk on npm
MyRx-Mail — Electron desktop client
🔄 In Progress (Phase 5)
ONC-ACB certification body engagement — CHPL listing in progress
Two dedicated portals — one for patients, one for providers — each purpose-built for their workflow.
Patient Portal
Full health record access — FHIR R4 (20+ resource types)
AI assistant + personal health coach
Consent management — grant or revoke instantly, on-chain
Prescriptions, lab results, vitals, immunizations
Emergency access card with NFC tap support
CMS Blue Button 2.0 (Medicare) — live; commercial payer integrations under discussion (architecture verified, not executed)
Credential Identity — your sovereign health profile
Appointment scheduling + telehealth video
Provider Portal
ONC (g)(10) standardized API test — PASS — (g)(10) PASS April 17, 2026
EPCS prescribing — DEA 21 CFR Part 1311 aligned (third-party audit in progress)
FHIR R4 patient records + CMS Blue Button 2.0 connection (commercial payer integrations under discussion)
SOAP notes with AI-assisted ICD-10 + CPT coding
Hyperledger consent trail — every access immutable
Drug recall alerts via FDA openFDA; drug-interaction advisories subject to prescriber judgment
Recall alerts delivered at point of prescribing
Lab ordering — Quest / LabCorp routing
🔐 Security Architecture (Both Portals)
MyRx-Sentinel v2.0 — DoD STIG hardening standards applied compliant
Fullscreen lock + screenshot guard in clinical mode
HIPAA idle timeout — auto-logout after inactivity
AES-256-GCM encryption at rest · TLS 1.3 in transit
Zero PII on-chain — only SHA-256 hashes + FHIR resource IDs
🌐 Access
Patient portal — patients.myrxwallet.io
Provider portal — providers.myrxwallet.io
Both portals accessible via ehr.myrxwallet.io
Mobile-responsive — iOS + Android compatible
MyRx-Mail desktop client — Electron app available
Health Intelligence
Curated health policy, interoperability updates, FDA alerts, and MyRxWallet platform news — sourced from federally-recognized agencies.
📋 ONC Finalizes TEFCA Exchange Protocols
The Office of the National Coordinator published updated TEFCA exchange framework rules, expanding the Qualified Health Information Network (QHIN) pathway. MyRxWallet is preparing its Phase 6 QHIN application in alignment with these rules.
💊 FDA Drug Recall Alert System — Live
MyRxWallet's prescribing module now integrates FDA openFDA drug recall alerts at the point of prescribing. Providers receive instant inline warnings when prescribing a recalled medication.
🔒 HIPAA Security Rule Modernization — 2026
HHS finalized amendments to the HIPAA Security Rule requiring enhanced encryption standards, multifactor authentication, and new audit logging requirements. MyRxWallet exceeds all updated standards with AES-256-GCM + TLS 1.3 + Hyperledger audit trail.
📡 CMS Interoperability Rules — Payer API Expansion
CMS finalized expanded payer API mandates requiring all MA, Medicaid, CHIP, and QHP plans to publish SMART on FHIR APIs. MyRxWallet's CMS Blue Button 2.0 (Medicare) integration is live; commercial payer integrations are architecturally verified against published SMART on FHIR endpoints with onboarding agreements under discussion.
🏛️ USCDI v7 Comment #703 — On Federal Record
MyRxWallet filed Comment #703 to USCDI v7 on April 11, 2026, proposing "Patient Digital Identity Credential" as a new national data class. This positions the MyRx Credential as a federally-recognized health identity standard.
✅ ONC (g)(10) Inferno — Full PASS
MyRxWallet completed the ONC Inferno v8.0.0 (g)(10) standardized API test suite with a full PASS across all 317 sub-tests on April 17, 2026. This is the platform's federally-attested interoperability certification.
Press Room
Official press releases, breakthrough announcements, and regulatory milestones — all on the public record, all independently verifiable.
Loading press releases…
📬
Media Inquiries
For press inquiries, interview requests, or media kit: info@myrxwallet.io · MyRxWallet North America Corporation · Las Vegas, NV
Global Partnerships
MyRxWallet's international partnership framework — GDPR-aligned, built for cross-border health data sovereignty.
🌍 International Standards
FHIR R4 IPS — International Patient Summary support
GDPR Article 9 — special health data category compliance
ISO 27001 — information security management aligned
HL7 International — global interoperability framework
WHO ICD-10/ICD-11 — international diagnosis coding
🤝 Partnership Categories
Health system integrations — payer + provider networks
Government health agency API connectors
Pharmaceutical and clinical trial data partnerships
Academic medical center research agreements
International telehealth network expansion
🏗️ Infrastructure Design
Self-hosted Hyperledger — no third-party cloud dependency
Multi-region deployment capable — no US-only lock-in
FHIR R4 base spec — universal across health jurisdictions
Consent layer — maps to GDPR, PIPEDA, PDPA frameworks
No PHI on-chain — architecture is jurisdiction-agnostic
📋 Engagement Model
White-label EHR licensing — full branding + customization
API integration agreements — revenue share available
Research participation programs — IRB-governed consent
Contact: info@myrxwallet.io to begin conversations
Fee Schedule
Transparent, publicly-auditable platform fee structure — no hidden charges, no data brokering, no surprises.
Platform Philosophy
Platform fees are charged exclusively for verified services delivered under written service agreements. Patients are never charged to access their own health records.
📋 Fee Structure
Fees are charged only under written service agreements
All fees cover operating costs and regulatory compliance
No profit-sharing, royalty, rebate, or token-value distribution
Patients are never charged to access their own health records
Fee categories: API access, EHR licensing, EPCS per-prescription, integration engineering
🏥 Who Pays What
Patients: $0 — record access is always free
Providers: Per-transaction micro-fee under service agreement
Partners: API access under signed service agreement
Researchers: Consent event fee per participant enrolled
Payers: Data exchange governed by CMS interoperability mandate
🔍 Transparency Commitments
Every fee publicly auditable — on-chain transaction log
No hidden charges — fee type disclosed before transaction
No data brokering — PHI never sold to third parties
No subscription fees for patients — free access always
Provider pricing: contact info@myrxwallet.io
Registrations & Filings
MyRxWallet's complete federal and regulatory registration record — every identifier, every filing, on record.
🏛️ Federal Business Identifiers
CAGE Code: 9VNZ7
Unique Entity ID: MVKQW9DKKGB8
NAICS: 518210 (Data Processing & Hosting)
SIC: 7374-00 (Computer Processing & Data Prep)
SAM.gov: Active registration
EIN and other sensitive identifiers available upon verified request — info@myrxwallet.io
🏥 Health Industry Registrations
NPI × 3 — multiple National Provider Identifiers
ONC Developer Registration — 10 SMART on FHIR client IDs
Electronic prescribing architecture aligned with 21 CFR Part 1311 (third-party audit in progress)
ONC (g)(10) Standardized API — PASS April 17, 2026
Inferno v8.0.0 — 317/317 sub-tests PASS
SMART App Launch 2.0.0 — Inferno test PASS
Bulk Data 2.0.0 — Inferno test PASS
US Core 6.1.0 — 20 resource types
📋 Federal Filings & Engagements
USCDI v7 Comment #703 — patient digital identity credential
FDA CDER concept paper — DSCSA/interoperability (pending)
HSCC CWG — Health Sector Cybersecurity Council engagement
ONC Developer Portal — registered API developer
Corporate HQ: MyRxWallet North America Corporation
ONC Health IT Certification
(g)(10) Standardized API — Inferno test PASS as of April 17, 2026.
Important Distinction
Passing the Inferno (g)(10) standardized API test suite is a prerequisite to, and is not equivalent to, ONC Health IT Module certification. ONC Health IT Module certification is issued by an ONC-Authorized Certification Body (ONC-ACB) and results in a listing on chpl.healthit.gov. MyRxWallet is progressing through that certification process; this page does not represent the Company as CHPL-listed until that listing occurs.
Granular scopes (v1 + v2) with sub-resource filtering
Bulk Data 2.0.0 with _since parameter
US Core 6.1.0 — 20 resource types
Why It Matters
The (g)(10) Inferno test pass is a federally-administered validation of identity, authentication, and consent infrastructure. It validates that patients can access their health data from any ONC-certified app using open standards. It is the platform's single most valuable interoperability milestone to date.
EPCS Prescribing
Electronic Prescribing for Controlled Substances — architected for 21 CFR Part 1311 compliance; third-party audit in progress.
EPCS Authorization
Electronic prescribing architecture aligned with 21 CFR Part 1311 (third-party audit in progress) — electronic prescribing live
21 CFR Part 1311 aligned; third-party audit in progress
Two-factor authentication required for all controlled substance Rx
Identity proofing — NPI + OIG LEIE verified
Logical access controls — per-provider scoping
Clinical Workflow
Provider signs Rx with two-factor authentication designed to 21 CFR Part 1311 (audit in progress)
Prescription anchored to Hyperledger — tamper-proof
Patient receives Rx in FHIR MedicationRequest format
Drug interaction checker inline — FDA database
Recall alerts delivered at point of prescribing
HIPAA / HITECH
Privacy and security rules enforced by architecture — not by policy promises.
HIPAA Compliance
PHI encrypted at rest (AES-256-GCM) and in transit (TLS 1.3)
Zero PII stored on-chain — only SHA-256 hashes and FHIR resource IDs
Consent-gated access — no data without explicit patient authorization
Minimum necessary standard — enforced at OAuth scope level
BAAs required for all vendors touching PHI
HITECH & Audit Logging
Breach notification procedures — 60-day maximum
Audit logging — every PHI access recorded
HIPAA §164.312(b) — audit controls implemented
6-year retention — logs never truncated
FHIR AuditEvent resources — queryable via certified API
Inferno (g)(10)
ONC Inferno test suite results — PASS on all items as of April 17, 2026.
Test Results
SMART App Launch 2.0.0 — PASS
Bulk Data 2.0.0 — PASS
US Core 6.1.0 — PASS (all 20 resource types)
Token introspection — PASS
Token revocation — PASS
Granular scopes v1 + v2 — PASS
Regression Policy
All (g)(10) test items must remain PASS before any PR merges to main. The Inferno test suite is run against the branch endpoint. TLS posture is verified (SSL 2/3 + TLS 1.0/1.1 rejected; TLS 1.2/1.3 accepted). This Inferno test pass is the platform's single most valuable interoperability milestone to date.
FHIR R4 Live
Full FHIR R4 implementation — 40+ endpoints, US Core 6.1.0, live at ehr.myrxwallet.io.
FHIR Endpoints Live
Patient, Practitioner, Organization
Condition, Observation, MedicationRequest
AllergyIntolerance, Immunization, Procedure
DiagnosticReport, DocumentReference
ExplanationOfBenefit, Coverage, Goal
AuditEvent, Consent, Device
Standards Compliance
FHIR R4 (4.0.1) — base specification
US Core 6.1.0 — profile conformance
USCDI v3 — data class coverage
SMART App Launch 2.0.0
Bulk Data 2.0.0 with _since parameter
🔬 Clinical Resources
Patient · Practitioner · Organization
Condition · Observation · MedicationRequest
AllergyIntolerance · Immunization · Procedure
DiagnosticReport · DocumentReference
💳 Financial & Coverage
ExplanationOfBenefit — claims history
Coverage — insurance detail
CoverageEligibilityRequest/Response
AuditEvent · Consent · Device
🔗 API Base URLs
FHIR Root: ehr.myrxwallet.io/api/v1/fhir/r4
Auth: ehr.myrxwallet.io/oauth/authorize
Token: ehr.myrxwallet.io/oauth/token
Discovery: /.well-known/smart-configuration
Bulk: /\$export (system-level)
Payer Connectivity
SMART on FHIR client architecture supporting the published payer APIs of major US insurers.
Active Connections
CMS Blue Button 2.0 — Medicare beneficiary data — LIVE
Architecture Tested Against
Published SMART on FHIR endpoints of major US payers (architecture verified; commercial onboarding agreements under discussion, not executed)
Data Retrieved (CMS Live)
ExplanationOfBenefit — claims history
Coverage — insurance details
Patient — demographics
Medication dispensing history
AI agents pull automatically on patient consent
Member Benefits
Three layers of platform capability — AI, infrastructure, and marketplace.
🤖AI Layer
1
MyRx-Assistant
Conversational health AI
2
MyRx-ClinicalAI
SOAP notes, ICD-10, CPT
3
MyRx-HealthCoach
Daily wellness guidance
🏗️Platform
1
MyRx-Gateway
WireGuard zero-trust VPN
2
MyRx-Telehealth
Video + scheduling
3
MyRx-Mobile
iOS and Android apps
4
MyRx-MedTracker
Medication adherence
5
MyRx-Emergency Card
NFC instant access
🛒Marketplace
1
MyRx-Marketplace
Health product catalog
2
MyRx-Pharmacy
Prescription fulfillment
3
MyRx-Insurance
Plan information reference
Veterans & CSOS
Controlled Substances Ordering System compliance and Veterans Health Administration integration pathways.
Veterans Support
VA Lighthouse API architecture compatibility (no executed VA agreement)
CCN-compatible architecture (no executed VA agreement)
VHA patient record portability
VA formulary integration
CSOS Compliance
DEA CSOS — Controlled Substances Ordering System
Electronic ordering of Schedule I–V substances
Digital certificates for CSOS authentication
Audit trail integration — every order on-chain
Family & Pediatric
Family account linking, pediatric record management, and guardian consent frameworks.
Family Accounts
Guardian-linked accounts for minors under 18
Pediatric FHIR profiles — US Core Pediatric Weight/BMI
Age-of-majority transition workflow
Sibling record linking with consent inheritance
Consent Architecture
Guardian consent on behalf of minor — HIPAA compliant
Consent transfer at age of majority
Adolescent privacy — 42 CFR Part 2 sensitive categories
Family health history aggregation
Risk Elimination
How MyRxWallet's architecture eliminates the most common healthcare data risks.
Technical Controls
AES-256-GCM encryption — at rest and in transit
Zero Trust architecture — no implicit trust at any layer
MyRx-Sentinel v2 — DoD STIG hardening standards applied compliance
WireGuard VPN — all traffic over encrypted tunnel
Credential-keyed port access — no open endpoints
Operational Controls
Zero PII on-chain — only hashes and FHIR resource IDs
We don't just meet the minimum — we build infrastructure that makes non-compliance structurally impossible.
Architecture as Compliance
Every HIPAA control at MyRxWallet is enforced by code, not policy. PHI cannot reach the blockchain — the chaincode rejects it at the protocol layer. Consent cannot be bypassed — OAuth scopes enforce it at the API layer. Audit logs cannot be deleted — they are append-only on Hyperledger.
Proactive Engagement
USCDI v7 Comment #703 — shaping national standards
HSCC CWG — health sector cybersecurity council
FDA CDER — concept paper filed April 2026
ONC 10 SMART client IDs — registered developer
Inferno (g)(10) — full test suite PASS
TEFCA / QHIN
Trusted Exchange Framework and Common Agreement — national health information network participation.
TEFCA Pathway
QHIN application planned — Phase 6
Patient-as-requester conduit model
SMART on FHIR certification prerequisite — in progress
TEFCA establishes the rules of the road for nationwide health information exchange. As a QHIN member, MyRxWallet will be able to query and respond to patient record requests across all participating networks — giving patients truly universal record portability.
Developer API
40+ live FHIR R4 endpoints, SMART on FHIR OAuth 2.0, Bulk Data 2.0.0 — production-ready at ehr.myrxwallet.io.
🔑 Authentication
OAuth 2.0 + PKCE — SMART App Launch 2.0.0
Authorization: /oauth/authorize
Token: /oauth/token
Introspect: /oauth/introspect
Revoke: /oauth/revoke
10 registered SMART client IDs available
📡 FHIR Endpoints
Base: /api/v1/fhir/r4/[Resource]
20 US Core 6.1.0 resource types
Bulk export: /\$export with _since
Search, read, create, update supported
Granular scopes v1 + v2
📦 SDK & Tools
Credential SDK: @myrxwallet/credential-sdk (npm)
Install: npm install @myrxwallet/credential-sdk
Discovery: /.well-known/smart-configuration
Capability: /api/v1/fhir/r4/metadata
Inferno (g)(10) — full PASS, all 317 tests
🔐 Developer Access
Contact: info@myrxwallet.io to request client ID
Sandbox environment available on request
Rate limits: documented per scope tier
Webhook events: consent grant / revoke
Org: myrx-token on npm (owner: myrxwallet)
Standards Conformance
Products and modules that have passed published standards tests. Full ONC Health IT Module certification via ONC-ACB is in progress.
Standards Conformance — Test Results
MyRxWallet EHR — ONC (g)(10) Inferno test suite PASS
FHIR R4 API — US Core 6.1.0 compliant
SMART App Launch 2.0.0 — Inferno test PASS
Bulk Data 2.0.0 — Inferno test PASS
EPCS Module — designed to DEA 21 CFR Part 1311 (third-party audit in progress)
EPCS Products
Electronic Prescribing for Controlled Substances — architecture designed to 21 CFR Part 1311; third-party audit in progress.
EPCS Module
Two-factor authentication designed to 21 CFR Part 1311 (audit in progress)
Controlled substance Rx — Schedule II–V
Identity proofing at provider onboarding
Logical access controls per provider
Every Rx anchored to Hyperledger — immutable
Integrations
Native integrations built into the platform — no third-party middleware required.
Clinical Integrations
CMS Blue Button 2.0 SMART on FHIR connection — live; commercial payer connections under discussion
FDA openFDA — drug recall alerts live
NPI registry — provider verification
OIG LEIE — exclusion screening
Quest / LabCorp — lab order routing
Platform Integrations
Hyperledger Fabric — consent and identity ledger
WireGuard — zero-trust network overlay
SMTP + MyRx-Mail — secure messaging
Twilio — SMS alerts (optional)
Webhook events — consent grant/revoke
Partners
Strategic partnerships that extend MyRxWallet's reach and capabilities.
Academic medical centers — research consent programs
Government agencies — ONC, HHS, FDA engagement
Become a Partner
MyRxWallet offers white-label EHR licensing, API integration agreements, and research participation programs — all governed by signed service agreements. Contact us to discuss partnership opportunities.
Consultation
Schedule a consultation with the MyRxWallet team.
Book a Consultation
Whether you're a provider evaluating the EHR, a partner exploring API integration, or a health system considering white-label deployment — our team is available for a direct conversation. Contact: info@myrxwallet.io
Downloads
Resources, documentation, and technical specifications available for download.
Available Resources
FHIR Capability Statement (JSON)
SMART Configuration (JSON)
ONC (g)(10) test results
Fee schedule PDF
MyRx Credential SDK documentation
Data Import
Patient-initiated health record import from any FHIR-connected source.
Import Sources
CMS Blue Button 2.0 (Medicare) — automated on consent; commercial payer connections under discussion
FHIR R4 bulk import — any compliant EHR
CCD/C-CDA document import
Lab result PDF parsing — AI-assisted
Wearable device data — HL7 FHIR Observations
HIPAA Notice
Your rights under the Health Insurance Portability and Accountability Act.
Your HIPAA Rights
Right to access your PHI — free within 30 days
Right to correct inaccurate health information
Right to know who has accessed your data
Right to restrict certain uses and disclosures
Right to receive a Notice of Privacy Practices
Our HIPAA Obligations
We only use PHI for treatment, payment, and operations
We never sell PHI to data brokers — ever
We notify you within 60 days of any breach
All staff with PHI access complete HIPAA training
BAAs executed with all business associates
⚠️ Violation Reporting
File a HIPAA complaint: HHS Office for Civil Rights
OCR hotline: 1-800-368-1019
Internal complaints: info@myrxwallet.io
We investigate all complaints within 30 days
No retaliation for good-faith HIPAA complaints
📋 Notice of Privacy Practices
Effective Date: January 1, 2025
We use PHI only for treatment, payment, and healthcare operations
We never sell your health data — to anyone, ever
You may request a paper copy of this Notice at any time
Contact: info@myrxwallet.io for full NPP document
Patient Consent
Informed consent framework — every access event recorded permanently on-chain.
How Consent Works
Patient grants consent via QR, NFC tap, or in-app
Consent event recorded to Hyperledger consent-channel
FHIR Consent resource created — queryable via certified API
Minimum necessary — scoped to specific resource types
Audit trail — every grant and revoke permanently recorded
42 CFR Part 2 — sensitive categories protected separately
GDPR Article 9 — special health data protections applied
📱 How to Grant Consent
QR code scan at point of care
NFC tap — credential card or phone
In-app — patient portal consent manager
Verbal consent + provider-initiated — witnessed and recorded
Each grant is scoped to a specific provider + visit window
🚫 How to Revoke Consent
Patient portal → Consent Manager → Revoke
Revocation is immediate — on-chain within seconds
Revoked consent cannot be re-read retroactively
Revocation event recorded as FHIR Consent resource
Contact info@myrxwallet.io for emergency revocation
Registrations & Trust
Our complete regulatory registration record — every federal identifier and certification on record.
🏛️ Federal Identifiers
CAGE Code: 9VNZ7
SAM.gov Unique Entity ID: MVKQW9DKKGB8
NAICS: 518210 · SIC: 7374-00
🏥 Health Registrations
NPI × 3 (multiple provider identifiers)
ONC Developer — 10 SMART client IDs
DEA EPCS — architecture aligned to 21 CFR Part 1311; third-party audit in progress
USCDI v7 Comment #703 — April 11, 2026
✅ Certifications on Record
ONC (g)(10) — PASS April 17, 2026
Inferno v8.0.0 — 317/317 sub-tests PASS
SMART App Launch 2.0.0 — Inferno test PASS
Bulk Data 2.0.0 — Inferno test PASS
SMART Configuration
Our SMART on FHIR well-known configuration — live and publicly queryable.
SMART Endpoints
Authorization: /oauth/authorize
Token: /oauth/token
Introspect: /oauth/introspect
Revoke: /oauth/revoke
Discovery: /.well-known/smart-configuration
Supported Capabilities
PKCE — required for all public clients
Asymmetric + symmetric client auth
Granular scopes v1 + v2
Refresh tokens — 90-day minimum
SMART App Launch 2.0.0
🔐 Token Details
Access token lifetime: 3600 seconds (1 hour)
Refresh token lifetime: 90 days minimum
Token format: JWT (signed)
Token introspection: active/inactive + scope list
Refresh grants new access token without re-auth
📋 Scope Format Examples
patient/Patient.read — patient demographics
patient/Observation.read — vitals + labs
patient/*.read — all patient resources
system/Patient.read — bulk/system-level
launch/patient — EHR-launched context
FHIR R4 Capability
Full list of supported FHIR R4 resources, search parameters, and interactions — live on ehr.myrxwallet.io.
👤 Patient & Clinical
Patient — demographics, contact, identifiers
Practitioner — provider profile + credentials
PractitionerRole — specialty + organization link
Organization — health system entity
Condition — diagnosis + problem list
Observation — vitals, labs, social history
💊 Medications & Orders
MedicationRequest — Rx + EPCS
MedicationDispense — pharmacy fulfillment
AllergyIntolerance — allergy + adverse reactions
Immunization — vaccine history
Procedure — clinical procedures
ServiceRequest — lab + imaging orders
📋 Documents & Results
DiagnosticReport — lab + imaging results
DocumentReference — CCD, SOAP, clinical docs
CarePlan — care coordination
Goal — patient health goals
Encounter — visit history
Location — facility + address
🔒 Consent & Coverage
Consent — on-chain consent record
Coverage — insurance plan detail
ExplanationOfBenefit — claims history
AuditEvent — access log (FHIR queryable)
Device — connected device records
RelatedPerson — guardian / family link
USCDI v7 #703
United States Core Data for Interoperability — Comment #703, filed April 11, 2026.
Our Submission
MyRxWallet filed USCDI v7 Comment #703 proposing "Patient Digital Identity Credential" as a new national data class — establishing that a patient's sovereign health identity credential is a first-class USCDI data element, not an afterthought. This aligns our NFT Credential architecture with federal interoperability standards.
Strategic Significance
Contributes the Patient Digital Identity Credential framework to the public USCDI v7 comment record
Comment #703 proposes adding "Patient Digital Identity Credential" as a new USCDI data class — a patient's sovereign, consent-anchored health identity. If adopted, this would make the MyRx Credential architecture a federal interoperability standard, not just a platform feature. Filed April 11, 2026. Public record at healthit.gov.
Clinical AI Disclosure
Administrative and informational use only — not FDA-cleared medical devices.
FDA SaMD Disclosure — Read Before Use
MyRx-Assistant, MyRx-HealthCoach, and MyRx-ClinicalAI are administrative and informational tools. They do not diagnose, treat, cure, mitigate, or prevent any disease or medical condition. They are not FDA-cleared as Software as a Medical Device. Any clinical output is presented to a licensed healthcare provider for independent review and clinical judgment. Patients should not rely on AI output in place of consultation with a qualified healthcare provider.
🤖 Tool Scope
MyRx-Assistant — information retrieval and administrative assistance only
MyRx-HealthCoach — general wellness information; not a substitute for medical advice
MyRx-ClinicalAI — provider-facing administrative drafting of SOAP notes, ICD-10, and CPT suggestions, always subject to provider review and sign-off before clinical use
💊 Drug-Related Features
Drug recall notifications display information retrieved from the FDA openFDA public dataset. Any drug-interaction information displayed in the provider workflow is advisory only and is subject to the prescribing provider's independent judgment and separate FDA-cleared drug-interaction software where clinically required.
⚖️ Regulatory Status
Not FDA-cleared as a medical device
Not a diagnostic tool — no clinical decisions made by AI
All AI output requires licensed provider review before clinical use
FDA CDER concept paper submitted (no regulatory response received)
AI features operate under 21st Century Cures Act administrative use exemption