Operations software around the clinic day, not a clinical decision system

Healthcare organizations run on appointment books, encounter types, provider templates, no-show rules, referral intake, prior-auth packets, and billing workqueues. We can build or integrate software for those operational jobs. This is not medical advice. We do not diagnose, treat, or claim to be a certified EHR. We do not advertise HIPAA certification we have not earned. If your project stores protected health information, your legal, security and (where applicable) HIPAA program remain yours. We will say when we are the wrong vendor.

What we will and will not touch

We will discuss scheduling templates (session lengths, overbooking rules you define, rooms, equipment), waitlists, reminder preferences, and staff workqueues for incomplete packets. We will discuss records-adjacent workflows: moving a document to a charting system via an interface you already use, tracking that a packet is complete, or giving a coordinator a queue. Completeness of a packet is not a clinical judgment.

We will not build a consumer “symptom checker” that implies care, an autonomous agent that messages patients about clinical content without your clinicians’ protocol, or a system that pretends to replace your EHR’s legal medical record. If you need an EHR, buy one in that market and hire implementers who live there.

AI in this industry is a heightened risk. Transcription or classification behind a clinician’s review is a different product than unattended advice. We default to human review on anything patient-facing. Model vendors’ data-use terms must be acceptable to your counsel, we will not hide a training-data clause behind a demo.

Operational problems (not clinical claims)

• The book is a shared calendar plus sticky notes

  Double-books, missing encounter types, and no-show patterns nobody can report. Scheduling software is operations.

• Intake packets stall the slot

  Consents, IDs, referrals. A coordinator queue with statuses beats a front-desk pile.

• Reminders that violate preference or content rules

  SMS/email must honor opt-out and must not include clinical detail you did not approve. Templates are a policy artifact.

• Referral intake is fax archaeology

  Workqueue, duplicate person matching, and a handoff into the system of record you name, not a second chart.

• Billing workqueue is tribal

  Claim holds for missing charges or auth. We can build the queue; we are not your RCM vendor of record unless scoped.

• Staff access after hours

  Role design: front desk versus billing versus a provider. Least privilege is not optional here.

Capabilities we will consider

• Appointment scheduling against provider templates and resources you define
• Intake and document completeness tracking (not clinical interpretation)
• Staff workqueues and SLAs for coordinators
• Interfaces to an EHR or PM system you already run, using their documented APIs or HL7/FHIR where you have an integration engine
• Identity, audit logs, and environment separation suitable for a security review you lead
• Explicit refusal of features that would constitute unlicensed practice or implied diagnosis

Use cases

• Clinic or group practice operations

  Scheduling plus packet queues beside an existing EHR, not a rewrite of the chart.

• Health-adjacent services

  Wellness, dental admin, veterinary ops, still careful with records; still not medical advice. Scope names the sector.

• Operational SaaS for clinics

  If you sell software to providers, tenancy and BAAs are product requirements. We still will not claim HIPAA certification for Progley as a badge.

• Internal tools for a larger organization

  A specific workflow (credentialing tracker, equipment booking) with IAM you specify.

How healthcare-adjacent work runs

1. Fit and constraint call

   What data, which regulations you assert, whether a BAA is required, and whether we should decline.

2. Discovery with compliance in the room

   Your privacy officer or counsel should see the data-flow diagram. We will not skip this to “move fast.”

3. Scope that names PHI

   If PHI is in scope, hosting, logging, subprocessors and access are written. If it is not, we keep it out on purpose.

4. Architecture

   Least privilege, audit, encryption in transit, and no casual use of consumer AI tools on records.

5. Launch

   Your change control. Training for coordinators. A way to turn a feature off. Iterate on the workqueue, not on clinical content.

Questions we hear first

Related

• Business management systems
• Business automation
• AI development (with review)
• Custom software
• Privacy policy
• Process
• Contact

Describe the operational job, not a diagnosis

Scheduling, packets, or a staff queue, plus whether PHI is involved. We will tell you if we can engage, what we refuse, and what your counsel must still own.

Start a Project