Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
Steven James Consulting

49 members • Free

GHL Command

42 members • Free

TopOfMind AI Builders

562 members • Free

AI Builder School

643 members • $21/month

The Ai Agency - Free Resources

1.7k members • Free

AI Agents Academy

888 members • Free

The HighLevel™ Launchpad

1k members • Free

Automation Station

3.4k members • Free

2 contributions to GHL Command
HIPAA
I noticed that you are using examples of clinics. Is your system HIPAA compliant? I have not done anything with any client with patients involved because I am not sure about this. My understanding is that even collecting information from patient leads could be affected by HIPAA compliance. I know it is possible. I just don't know how to do it, so I thought I'd ask you how you were ensuring compliance.
1 like • 10d
This is a really important question. HIPAA isn’t something you want to assume you’re covered for just because the tech can handle the workflow. The data being collected, where it’s stored, and the agreements with the vendors all matter. Definitely worth getting the compliance side clear before building for clinics.
Read the Account Back Before You Sign Off
Command note: a build is not finished when the builder reports success. It is finished when the account says the same thing. Shipped today: Verify stopped trusting the build's own report and now reads the sub-account back. Every object the plan asked for — pipelines, stages, custom fields, tags, calendars, forms, workflows, templates — gets looked up in the account and reported found or missing, one line each. What changed under that: • "Not checked" now counts as a defect, not a pass • A read that fails is reported as unreadable, never as fine • One marked test lead goes through the real form, gets watched in, and the test contact is deleted — and it tells you before it does that • Workflows arrive as drafts, so nothing fires at a client before a person has read it The report also went from 46 printed pages to 8. A verification nobody reads is not a verification. Steal the method even if you never touch our tool: 1) Write down what you said you would build, by name, before you build it. 2) After the build, open the account and find each item yourself. 3) Anything you could not check is unknown — never mark it done. 4) Push one test record through the real entry point, then delete it. 5) Sign off only on what you actually saw in the account. Every builder reports success. Only the account can confirm it.
Read the Account Back Before You Sign Off
1 like • 10d
100% agree. A build isn’t really done just because everything saved without errors.Testing it with a real contact through the actual entry point is where you catch the stuff you didn’t see while building.
1-2 of 2
Arham Abid
1
3 points to level up
@arham-abid-3029
I am Arham Abid. A 27 year old entrepreneur. Featured in Forbes. Founder of the most reliable VA agency. Founder of the fastest growing HL Agency

Active 9d ago
Joined Aug 25, 2026