For members of the CMS Health Tech Ecosystem, pharmacies, pharmacy system vendors, networks, payers, and primary care teams.
An open, vendor-neutral pharmacy network connector. It shows a community pharmacy acting as a first-class interoperable provider: it receives the patient's records, matches and reconciles them, documents a test-and-treat visit, and returns the encounter to a CMS Aligned Network, which notifies the primary care provider. The network can also query the pharmacy for dispenses, fill status, and immunizations.
FHIR IQ built it, with HealthClaw and CareAgents.cloud providing the patient-facing side. It was built for the CMS Health Tech Ecosystem Pharmacies & Pharmacy Systems work group as a demonstration. It is not a CMS or HHS product and is not endorsed by CMS or HHS.
A Test & Treat loop discussed in the work group: (1) two front doors, a SMART Health Link QR from the patient or a Treatment query to the network; (2) patient matching; (3) reconciliation of the inbound medication list against pharmacy dispense history; (4) test, assess, treat, document; (5) return of the encounter summary and reconciled list to the network, which routes it to the primary care provider.
Real: the FHIR R4 exchanges between the parties, US Core 6.1.0 and SMP 1.0.0 resources (the return Bundle validates with zero errors in the HL7 validator), SMART Health Links with encrypted files, purpose of use bound to the access token, a demo subset of the CMS HTE patient-matching rules, renal dose adjustment from the network eGFR, adherence from fill history, Subscription notifications, and a pharmacy-side FHIR responder.
Simulated and labeled: the Aligned Network, the primary care EHR, the pharmacy dispensing system, the patient records (synthetic), and the messaging thread. Client authentication is real SMART Backend Services (private_key_jwt), but with published demo keys.
No. Every person and record is fictional. Please do not enter real patient information anywhere on this site, including the partnership form.
No new hardware. The patient starts from a text on the phone they already have. Pharmacy staff get a text with no patient details and open the visit in any browser. The connector runs beside the dispensing system and EHR the pharmacy already uses and exchanges data through FHIR APIs, rather than through a new install at the counter.
A production deployment still needs a network relationship, a business associate agreement, and an export or API from the pharmacy's dispensing system. The connector is designed so that one connection serves any Aligned Network.
The pledge asks pharmacies to connect to an Aligned Network bidirectionally, respond to patient and treatment queries with dispense data, fill status, immunizations, and medication history, and share pharmacist-identified medication issues and adherence signals with the care team. Each of those is a step in the demo; the overview page tracks them.
The demo assumes one. Many pharmacists bill under the pharmacy's organizational NPI today; this matters for National Provider Directory validation at scale and is flagged rather than solved here.
That is the goal of the CareAgents flow: the patient texts, the agent collects consent, hands a time-limited SMART Health Link to the pharmacy directly (never by text), books the visit, and returns the summary in the same thread. The patient is messaging their own agent, not the pharmacy, and records never travel in a message. Today CareAgents.cloud offers an iMessage line (in sandbox, sample records only) and web chat. RX Genie's relay endpoint already accepts SMS and RCS as channels; CareAgents support for them is planned. WhatsApp is not planned, because WhatsApp bars third-party general assistants. See the Messages tab for the flow.
Not on this site. The thread here is simulated and scripted, so it runs the same way every time on synthetic data. RX Genie exposes an inbound endpoint in the CareAgents relay format so the live iMessage line can drive the same flow; that hookup is a planned step, and real patient records will not travel by text until the messaging provider is under a business associate agreement.
Yes. Register a client with your JWKS URL to get tokens from the pharmacy responder and the mock network using your own keys (SMART Backend Services, ES256, ES384, or RS384), send returns, and have RX Genie fetch SMART Health Links from your host. Synthetic data only.
Through the Aligned Network: the pharmacy returns an encounter Bundle with a Task owned by the patient's PCP. The PCP's EHR works its network Task queue, fetches the encounter and visit summary under Treatment, and completes the Task, which closes the loop. A FHIR Subscription notification (id-only) is an optional fast path, because the draft CMS network specification defers Subscriptions. The practice's office line also gets a text with no patient details saying a summary is waiting. For practices without a network connection yet, delivery by Direct secure messaging or fax is planned, not built.
FHIR R4, US Core 6.1.0, USCDI v3, SMART Health Links, CARIN digital insurance card, HL7 Standardized Medication Profile 1.0.0, Subscriptions R4 Backport, FHIR Task and AuditEvent, SMART Backend Services (private_key_jwt), HL7 v3 PurposeOfUse (TREAT), and a demo subset of the CMS HTE patient-matching rules.
Yes, with synthetic data. The pharmacy responder publishes https://rxgenie.us/fhir/metadata and https://rxgenie.us/.well-known/smart-configuration. The mock network is at https://rxgenie.us/network/fhir/metadata. Tokens require a purpose of use.
Not that we could find in public material as of October 2026, which is why that leg is labeled mock. We would like to test against a network sandbox.
Pilots, implementation partnerships, network sandboxes, and standards collaboration are all welcome. Use the partnership form.