SITREP // DIAMOND EDGE TMS WEB REVIEW

D1amond Edge compliance review.
All sources cited. Unlike the original.
Did we improve it to position for Vancouver's potentially underserved Hispanic patients, cite all sources, correct HIPAA violations, and bring accessibility into compliance? If that's true, possibly. Census says Hispanic or Latino residents are 16.8% of Vancouver.
We have the watches, but we have the time ☠️

 DEFCON 1Cocked Pistol13 hits DEFCON 2Fast Pace17 hits 1.7

23 pages overstate what the treatment is cleared or proven to treat

Legal
Overview
Several pages claim or imply TMS effectively treats conditions where the site elsewhere admits coverage is narrower or use is off-label.
Description
The TRICARE page says TMS allows patients to maintain operational status while effectively treating depression, PTSD, anxiety, and OCD, then says the treatment effectively addresses treatment-resistant depression, mTBI, anxiety, OCD, and PTSD. The veterans page says TMS treats depression, PTSD, and anxiety and that it can address both PTSD and depression. The TRICARE blog says 70–80% of patients achieve at least a 50% symptom reduction, higher than the 50–60% figures used elsewhere. The OCD blog says FDA approval occurred in 2022 in the key takeaways, then 2018 in the body.
Impact
This reads as a false or at least overbroad clinical claim. mTBI is investigational. PTSD and anxiety are off-label in this context. TRICARE coverage is described elsewhere on the same page as primarily for treatment-resistant Major Depressive Disorder. Patients, military families, and referrers should not have to reconcile contradictory coverage and efficacy claims. The FTC health-products advertising guidance explains that health claims must be truthful, not misleading, and supported before dissemination; deceptive health advertising can lead to orders, corrective advertising, refunds, or civil penalties.
Solution
Rewrite the affected copy under clinician review. State treatment-resistant depression as the established covered indication; state OCD with the correct FDA-cleared year and "cleared" language; frame PTSD, anxiety, and mTBI as off-label, adjunctive, promising, or investigational only where accurate. Normalize response-rate language to the site's own 50–60% range unless a specific higher figure is clearly attributed to the exact protocol and population.
References
TRICARE coverage page — diamondedgetms.com/resources/tricare-coverage
TRICARE blog — diamondedgetms.com/blog/tricare-coverage-for-tms-therapy-what-military-families-need-to-know
Veterans blog — diamondedgetms.com/blog/tms-therapy-for-veterans-a-lifeline-for-mental-health-challenges
OCD blog — diamondedgetms.com/blog/innovative-approaches-to-ocd-treatment-tms-and-beyond
 1.9

38 of 43 existing posts publish health claims with zero source citations

Legal
Overview
The blog repeatedly makes clinical and statistical claims without linking the reader to the research those numbers supposedly come from.
Description
Thirty-eight of 43 existing posts reviewed had zero source citations. The highest-risk examples are not vague wellness copy; they include specific response rates, remission percentages, and symptom-score reductions, including Y-BOCS score reductions. Those are measurable clinical-performance claims. The FAA series, 10 posts, adds a separate quality problem: the posts have almost no Diamond Edge TMS brand presence in the body text, which makes them read like generic syndicated medical content rather than practice-reviewed patient education.
Impact
Unsupported statistics are harder to defend than general claims because the reader reasonably treats the number as evidence. A health-products claim does not become safer because it is published in a blog instead of on a service page. The same substantiation problem follows it: patients, referrers, and payers cannot tell whether the figure came from a peer-reviewed study, a device manufacturer, an unrelated protocol, or generated filler. The FAA posts also create a trust and provenance problem, because thin brand presence gives the practice little signal that a clinician reviewed, adopted, or stands behind the content.
Solution
Inventory all blog posts before publishing new ones. Add primary-source citations beside every response-rate, remission, score-change, clearance, and indication claim, or remove the number. For FAA posts, add practice-specific context, clinician review, and a clear relationship to Diamond Edge TMS services; otherwise archive or rewrite them. Keep a source log so future edits do not detach claims from their substantiation.
References
Blog archive — diamondedgetms.com/blog
FTC health-products advertising guidance — ftc.gov/business-guidance/resources/health-products-compliance-guidance
 1.10

Anxiety and Portland posts contain source-integrity errors

Legal
Overview
Some posts do cite sources, but the citation layer itself is unreliable: one anxiety post contains two critical citation errors, and a Portland post has an additional correction queued.
Description
The anxiety post has two separate source-integrity failures: the journal name is wrong, and the citation URL is completely wrong. That is different from merely omitting a citation. It tells the reader there is substantiation, then points them to the wrong authority. Separately, the Portland post error needs to be corrected now while the broader blog audit is still open.
Impact
A bad citation can be worse than no citation because it creates false confidence. Patients and referrers see a clinical claim dressed up as researched, but the citation trail does not support the claim as presented. In a health-claims context, that undermines the report's central pattern: the site needs substantiation that is specific, reachable, and matched to the exact statement being made. Wrong journal metadata and wrong URLs also make later legal, clinical, or regulatory review slower because every cited claim has to be re-verified from scratch.
Solution
Pause publication edits long enough to fix the anxiety post and the Portland post. For the anxiety post, replace the journal name and URL with the exact source actually supporting the claim, then re-check the surrounding sentence so the citation is not being overread. For the Portland post, correct the known error and add it to the same citation QA queue. Then run a post-by-post citation audit across the blog before relying on any of the existing source links.
References
Anxiety post — diamondedgetms.com/blog/mental-health-in-the-heat-can-hot-weather-affect-your-mood-or-anxiety
Blog archive — diamondedgetms.com/blog
FTC health-products advertising guidance — ftc.gov/business-guidance/resources/health-products-compliance-guidance
 1.11

Privacy notice on the site is the vendor's, not the practice's

Regulation
Overview
The practice must publish its own Notice of Privacy Practices. It currently publishes the website vendor's.
Description
Four policy links in the footer resolve to treatspace.com. All four were read. The one presented as a HIPAA statement describes Treatspace's practices as a business associate: its own staff, its own audit process, its Pittsburgh address and support email. It does not mention Diamond Edge TMS or Dr. Block. It contains no privacy contact, no complaint procedure, no right to complain to the Secretary of HHS, and no effective date.
Impact
45 CFR 164.520(c)(3)(i) requires a covered entity maintaining a services website to prominently post its own notice. The vendor document cannot satisfy this and cannot be adopted by editing, because it describes the opposite side of the business-associate relationship. Separately, notices had to be updated by 16 February 2026 to address 42 CFR Part 2 substance use disorder records, which reaches practices that merely receive such records.
Solution
Adopt an HHS model notice, complete the entity-specific fields, host it on the practice domain. HHS publishes them free, built to be filled in. Do it before any domain change so it moves with you.
References
45 CFR 164.520 — law.cornell.edu/cfr/text/45/164.520
HHS model notices — hhs.gov/hipaa/…/model-notices-privacy-practices
 1.12

The practice name is unregistered; the live “Diamond Edge” marks belong to toolmakers

Legal
Overview
“Diamond Edge TMS” has no federal trademark registration. The practice is trading on an unregistered name.
Description
A search of public USPTO records returns no registration for “Diamond Edge TMS”, and none for “Diamond Edge” in Class 44 (medical and healthcare services), the class this practice would file in. Three live “Diamond Edge” registrations do exist — all held by unrelated companies for unrelated goods: pocket knives (Reg. 2163516), circular saw blades (Reg. 4047922), and hair trimmers (Reg. 6336524). A fourth, Diamond Edge Technology, is dead. This was a public-records search, not a legal clearance opinion.
Impact
Trademark rights are class-specific, so cutlery and hair clippers are unlikely to conflict with psychiatric services — the practice is probably not infringing anyone. The exposure runs the other way. Without a registration the practice holds only common-law rights, which reach no further than the geographic area of actual use and are materially harder and costlier to enforce. Another clinic could register the name federally and obtain nationwide priority, including against this practice outside its immediate area. The public record of use is also inconsistent: the name is split across two domains, and at least one third-party directory lists the practice in Vancouver, British Columbia rather than Vancouver, Washington.
Solution
Have a trademark attorney run a clearance search and, if it comes back clear, file in Class 44. USPTO fees are a few hundred dollars per class; attorney time is additional. This is the owner’s decision and should be filed by the owner or their attorney — not by a contractor or agency. A USPTO application carries a declaration of ownership signed under penalty of perjury.
References
USPTO Trademark Search — tmsearch.uspto.gov
Trademark basics, common-law vs federal rights — uspto.gov/trademarks/basics/trademark-patent-copyright
 2.3

Click-to-call button fails the readable contrast threshold

Regulation
Overview
The phone button is below the contrast level required for readability. It is the primary way a patient reaches you.
Description
Automated accessibility testing flags four failures.
CONTROL                 COLOURS              MEASURED    REQUIRED
click-to-call button    white on #5e96ea      2.98 : 1     4.5 : 1
service page heading    white on #5e96ea      2.98 : 1       3 : 1
body links              #007bff on white      3.97 : 1     4.5 : 1
Impact
Patients include veterans and older adults. A phone number that is hard to read costs calls, independent of any standard. On whether it binds you: web accessibility is not settled under the ADA for private businesses, whatever accessibility vendors claim. But 45 CFR 84.84 makes WCAG 2.1 AA binding on practices receiving federal financial assistance, and HHS now treats Medicare Part B participation as qualifying. If you bill Part B, the date is 11 May 2027 at 15+ employees, or 10 May 2028 below that.
Solution
Darken the button background. A few shades clears the threshold. Part B participation determines whether the deadline applies and should be confirmed with the practice's billing function.
References
45 CFR 84.84 — law.cornell.edu/cfr/text/45/84.84
DOJ web guidance — ada.gov/resources/web-guidance
 2.8

Heading levels skip on six pages

Regulation
Overview
Screen reader navigation is degraded on six pages, which matters if the practice is subject to federal web-accessibility requirements.
Description
Six pages jump from a first-level heading straight to a third, and from second to fourth. Automated testing flags the sequence breaks.
Impact
People using screen readers navigate by moving between headings. Gaps in the sequence make a page harder to move through. By itself this is a technical accessibility defect; if the practice receives federal financial assistance, 45 CFR 84.84 makes WCAG 2.1 AA the relevant web standard on the federal timetable.
Solution
Correct the heading hierarchy in the website templates so each page follows a logical sequence.
References
45 CFR 84.84 — law.cornell.edu/cfr/text/45/84.84
 2.14

The insurance page has no main heading

Regulation
Overview
A carrier-facing page patients search for has no top-level heading, which weakens accessibility and page structure.
Description
The insurance page carries no main heading and very little visible text. That leaves assistive-technology users without the basic page landmark they expect when confirming coverage information.
Impact
Coverage pages are a common entry point for patients, including TRICARE families. If 45 CFR 84.84 applies, the site needs to be brought into WCAG 2.1 AA conformance on the applicable federal deadline. A missing main heading is a small fix, but it is still part of that compliance surface.
Solution
Add a clear page heading and carrier/plan text to the insurance page, with heading levels aligned to the rest of the template.
References
45 CFR 84.84 — law.cornell.edu/cfr/text/45/84.84
 2.19

Replying to online reviews with patient detail

Regulation
Overview
Not found on the site. Included because it sits beside something you do and is the clearest documented risk of its kind.
Description
Two of the penalties issued in this area went to dental practices that replied to negative reviews with details about the patient: confirming someone was a patient, correcting their account of a visit, naming a treatment. Both settled, at $10,000 and $23,000. In each case the disclosure was the trigger; a deficient privacy notice was found afterwards during the investigation.
Impact
The instinct to correct an unfair review is natural, and it is the instinct that produced both penalties. A patient may disclose their own care publicly. The practice replying in the same thread is a different act under different rules.
Solution
Never confirm someone is a patient, or reference any detail of their care, even to correct something false. A neutral reply inviting the person to call the office handles every case safely. Brief anyone with access to the Google Business Profile.
References
New Vision Dental agreement — hhs.gov/hipaa/…/new-vision-ra-cap
 2.26

Website tracking may fall under Washington's health data law

Regulation
Overview
Flagged, not concluded. Requires follow-up before acting.
Description
The site runs Google Tag Manager with an advertising conversion tag. On a psychiatry practice's website, who visited and what they viewed can itself indicate mental health status.
Impact
Washington's My Health My Data Act is misread in both directions. Its HIPAA exemption operates at the data level, not the entity level: patient records are exempt, marketing analytics and advertising data about site visitors generally are not. The Act expressly reaches mental health status and location data indicating access to health services. Establishing what is actually transmitted needs more than a review of the pages supports.
Solution
A compliance advisor should determine whether the site's advertising and analytics tags are in scope. Live area; similar tracking on healthcare sites has drawn attention elsewhere.
References
RCW 19.373 — app.leg.wa.gov/RCW/default.aspx?cite=19.373