
NeuroTap: A HIPAA-Compliant Tapping Therapy App Built for Medicare Reimbursement
.avif)
Compliance
From day one
Integration
Medicare-ready
Clinical
Outcomes
Platform
iOS & Android
Scale
3 conditions, one app
One app. Three conditions. Every Medicare requirement met.
NeuroTap Health is the healthcare venture from Nick Ortner, founder of The Tapping Solution, a consumer app with more than 32 million guided sessions behind it. Tapping, also known as EFT, is a somatic technique. Guided by audio, a person taps through a fixed sequence of acupressure points, the eyebrow, the side of the eye, the collarbone, under the arm and others, while acknowledging how they feel. It is calm and uncomplicated, which is a large part of why it works.
It enrolls Medicare beneficiaries, measures their progress with the same clinical instruments a physician would use, and reports results to CMS so the care is reimbursed on outcomes rather than subscriptions. That meant rebuilding the experience on a clinical and regulatory foundation while keeping the part patients actually feel just as simple.
.avif)
What we were up against
The difficulty was not in any single feature. It was in making clinical rigor, Medicare integration, and a calm consumer experience coexist in one app.
Protected health information touched almost everything
Clinical scores, self-harm flags, and Medicare identifiers all flow through the product, while the same product needed product analytics and outbound CMS reporting. The data had to be partitioned so that PHI never reached a system that should not see it.
A wellness experience had to become a measured clinical protocol
Open-ended consumer content became structured programs with baseline assessments, scheduled reassessments, scoring thresholds, and graduation logic, all configurable rather than hardcoded so the clinical team could tune them over time.
Medicare reimbursement runs on live integrations
Eligibility, alignment, and outcome reporting each require a working CMS API connection and FHIR-formatted data, delivered against a fixed launch date with an earlier application cutoff before it.
None of it could complicate the tapping
Every layer of compliance and clinical machinery had to sit underneath an interface that still feels like pressing play and tapping along.
.avif)
NeuroTap set four goals for the build.
Qualify for CMS ACCESS
Build a working prototype in time for the application window, then deliver a compliant MVP for launch. No slipped deadlines, no compliance shortcuts.
Treat three conditions in one app
Anxiety, low mood, and chronic pain, separately or in combination. Seven adaptive program variants, one codebase.
Prove outcomes
Reimbursement tied to real clinical change. PHQ-9, GAD-7, WHODAS, and PROMIS scored automatically.
Protect every patient
HIPAA-grade security from sprint one, and a crisis safety net wired into the clinical flow for anyone in acute distress.
.avif)
The app we built
Momentum delivered a working app for iOS and Android from a single Flutter codebase, the Ruby on Rails backend that powers it, and the clinical and reimbursement systems around it. Here is what it actually does.
Medicare enrollment and clinical assessment
Onboarding captures Medicare details and informed consent before any clinical data is collected. PHQ-9, GAD-7, WHODAS, and PROMIS then set the baseline and track outcomes automatically throughout the program.
Adaptive tapping programs
Each condition runs as a structured program with reassessments on a fixed cadence. With multi-track enrollment, a patient can treat anxiety, low mood, and chronic pain at once, across seven dedicated program variants.
Session player and library
Guided sessions play audio alongside an animated avatar with on-screen tapping cues. Beyond structured programs, patients access roughly 200 sessions across eight categories, including Quick Taps for acute moments.
Clinical oversight and safety
When an assessment crosses a risk threshold, the app surfaces crisis resources and flags the event for review. The Medical Director dashboard gives full oversight of enrolled patients, scores, alerts, and CMS-ready exports behind role-based access.
.avif)
How it came together
Workshops and a proof of concept
A kickoff workshop and user story mapping turned a clinical vision into a buildable specification in time for the CMS application window.
Compliance reviewed before code
Every HIPAA requirement was approved by a dedicated compliance officer before a developer implemented it, then verified by QA before it closed.
A multidisciplinary team
Business analysts with healthcare backgrounds, Rails and mobile engineers, a product designer, DevOps, and QA worked against shared tickets and regular reviews.
Tight client feedback loops
Nick and his team tested builds through TestFlight and shaped features such as multi-track enrollment directly, with decisions turned around in days.
.avif)
The tech behind the build
Flutter, Ruby on Rails, and AWS formed the core. Every layer was chosen to keep PHI isolated and CMS reporting clean.
Flutter
Cross-platform iOS and Android from a single codebase. The tapping session player, clinical assessments, and multi-track program logic all run natively, with no web views.
Ruby on Rails
The backend powering enrollment, clinical scoring, adaptive program logic, and the Medical Director dashboard. Role-based access keeps PHI behind the right boundaries.
AWS
HIPAA-eligible infrastructure from day one. PHI lives here and nowhere else, with the architecture reviewed by a dedicated compliance officer before implementation.
FHIR R4
The data format for everything CMS touches: eligibility checks, alignment, and outcome reporting. Structured to meet CMS ACCESS requirements without custom workarounds.
.avif)
What we achieved together
By the CMS launch window, the full product was working end to end, from patient enrollment to Medicare reporting.
End-to-end enrollment
Patients enroll, consent, complete validated assessments, and move through an adaptive program across one or more conditions.
Clinical oversight, live
The Medical Director dashboard gives full visibility into enrolled patients, scores, self-harm alerts, and CMS-ready exports behind role-based access.
Patient experience delivered
The tapping player, session library, Quick Taps, and crisis safety flow are all in patients' hands.
Compliance verified
HIPAA security and CMS eligibility, alignment, and reporting integrations built, reviewed, and verified before launch.
Foundation for what's next
The architecture is built to grow: new conditions, new assessments, and new CMS programs can be added without rebuilding the compliance layer.
NeuroTap set out to take a method that has helped millions and make it work inside the demands of regulated healthcare, without losing what makes it effective. Momentum built the patient app, the clinical engine, the safety net, and the Medicare integration to do that, with compliance treated as part of the product from the first sprint. The app is live and the partnership continues.



.png)
.avif)