This document describes, precisely and completely, what MyRxWallet does and does not do. It is published for regulators, counsel, institutional partners, journalists, and any other party evaluating this platform.
Our scope is deliberately narrow. Our non-scope is technically enforced, not governed by policy alone. We do not ask to be trusted on either point — we ask to be evaluated on our architecture.
MyRxWallet North America Corporation is an infrastructure company building compliance-first Web3 systems for regulated environments, beginning with healthcare. We provide four infrastructure layers governed by a fifth: MRxDAO, the preeminent on-chain governing body of the ecosystem.
The following activities are technically impossible within our architecture. They are not restricted by policy — they are absent by design. There is no configuration, administrative override, or future flag that enables them without a fundamental rebuild of the system.
These are not policy commitments. The system cannot perform the following functions because the required components do not exist in the codebase.
MyRxWallet's architecture is engineered to operate within the following frameworks. This is not a claim of certification or regulatory approval. MyRxWallet is a development-stage company and holds no regulatory approvals at this time. These are the standards our system is designed to be consistent with.
| Authority / Standard | Relevance to Our System |
|---|---|
| HIPAA / HITECH | No PHI is stored or transmitted. The system is designed to avoid HIPAA-covered entity status by operating on hash-based provenance only. |
| HHS / ONC Interoperability Rules | FHIR R4-native API layer enables compliant data access patterns. Designed to support CMS CY2027 interoperability requirements. |
| FHIR R4 / R5 | All clinical data interfaces use HL7 FHIR-conformant resources. MedicationStatement, Patient, and Provenance resources are live and testable. |
| NIST Zero-Trust Architecture (SP 800-207) | Access decisions are identity-verified, policy-enforced, and logged per request. No implicit trust is granted by network location or prior session. |
| SEC Boundary Definitions | Platform functions are designed to fall outside broker-dealer, ATS, and investment adviser definitions. No securities are issued or facilitated. |
| Wyoming SF0038 (DAO LLC) | Governance layer references Wyoming's DAO LLC framework for on-chain organizational structure. No securities are associated with governance participation. |
| DSCSA / Drug Supply Chain Security Act | Drug provenance module supports Section 232 traceability requirements. Immutable hash-based chain-of-custody for pharmaceutical supply chain. |
| USCDI v3 / v4 | Identity and credential data elements align with U.S. Core Data for Interoperability standards. USCDI v7 comment submitted to ONC. |
| Wyoming SF0038 — DAO LLC / MRxDAO | MRxDAO is legally structured under Wyoming's DAO LLC statute, providing state-recognized legal standing for on-chain governance. MRxDAO serves as the preeminent governing body of the MyRxWallet ecosystem — issuing Platinum Grade classifications, monitoring compliance via Sentinel AI, and governing individual and entity participants in alignment with federal and state law. |
| FinCEN / BSA — AML/KYC | Sentinel AI Agent, operating under MRxDAO governance, provides continuous AML/KYC monitoring aligned with Bank Secrecy Act obligations. Anomaly detection and fraud screening are infrastructure-level functions. Final determinations are made through MRxDAO's governance process. |
MRxDAO is the preeminent governing body of the MyRxWallet ecosystem. It does not compete with or replace federal or state regulatory authorities. It is the highest governance layer within the ecosystem — structured to operate under law, enforce compliance, and issue verifiable standing to participants.
We are not asking to be trusted. We are asking to be examined.
Our architecture is our argument. MRxDAO is our governing standard. Sentinel AI is our monitoring layer. Our restraint is our credential.