Soulbound credential infrastructure for patient and provider identity, designed to bind cryptographic identity to the participant rather than to a device or account. Available through DAORX APIs for application integration.
Programmatic enforcement of patient consent profiles at the moment of data access. Applications submit access requests; DAORX validates against the participant’s pre-registered consent rules and returns access tokens only when consent matches.
Native unit of account on the sovereign chain for transaction settlement, with smart contract-enforced royalty distribution to rights holders on every value-bearing access event. Applications integrate against the rail; rights administration is handled at the protocol layer.
Cryptographic provenance for every consent event, every access event, every royalty distribution. Applications get audit-grade provenance built in, designed to satisfy HIPAA, regulatory inspection, and rights administration audit requirements without separate logging infrastructure.
DAORX is designed to support application developers across three engagement tiers. Specific terms, capacity allocations, and fee schedules are in development and will be published as the system advances toward production readiness.
| Tier | Description |
|---|---|
| Community | Open access for development, testing, and small-scale applications. Standard rail fees apply per transaction. Designed to support broad ecosystem participation. |
| Production | Higher-capacity tier for commercial healthcare applications. Reserved infrastructure capacity, defined service levels, integration support. |
| Enterprise | Dedicated infrastructure capacity reservations, white-glove integration support, healthcare-specific compliance certifications, custom service agreements. Designed for high-volume institutional applications. |
Healthcare applications face a structural problem: the regulatory, security, and consent infrastructure required to operate compliantly in healthcare is heavy. Most application developers either build their own from scratch — a multi-year effort — or use commodity cloud services that satisfy hosting requirements but leave consent enforcement, identity binding, audit trails, and rights administration as application-level work.
DAORX is designed to solve this at the infrastructure layer. Applications integrate against a rail that handles consent, identity, audit, and royalty distribution as native protocol features. The application focuses on its product; the rail handles the regulated infrastructure.
Developer documentation, API references, integration patterns, and sample applications will be published as DAORX advances toward production readiness. Healthcare application developers interested in early integration partnership are invited to contact MyRxWallet directly.