An optometry practice app lives or dies on recall, records and the prescription copy.

An eye exam record is protected health information

The refraction, the intraocular pressure reading, the retinal images, the prescription and the simple fact that someone attended are all health information about an identified person. A practice that transmits health information electronically in connection with a covered transaction, which for most practices means billing a plan, is a covered entity, and that information is protected health information in its hands. Moving it onto a phone does not change what it is.

The rule that decides your vendor list is the business associate rule. Anyone who creates, receives, maintains or transmits protected health information on the practice's behalf is a business associate, and you need a written contract with them. That contract has to establish the permitted and required uses and disclosures of the information, require the business associate to safeguard it, require it to report any use or disclosure the contract did not provide for, and it may not authorise anything the practice itself could not do under the Privacy Rule. A host, a database provider, a messaging vendor and a backup service can all land on that list.

So be plain about tools. Newly does not sign a business associate agreement, and its documentation and terms do not mention HIPAA or such an agreement at all. That does not stop you building a practice app, but it does decide where the records themselves live and who you sign with for that part. Before choosing anything, read what HIPAA actually requires of software, rather than what a product page implies.

HHS, business associate contracts and what they must require

The prescription copy is a rule, not a courtesy

Under the Federal Trade Commission's Eyeglass Rule, 16 CFR 456.2, it is an unfair act or practice for an optometrist or ophthalmologist to fail to give the patient one copy of the prescription immediately after the refractive eye examination is completed. You cannot condition the examination on an agreement to buy glasses from you. You cannot charge a fee as a condition of releasing the prescription. You cannot make the patient sign a waiver to get it.

Digital delivery is allowed, and the conditions read like a specification. 16 CFR 456.3 requires the prescriber to identify the specific method or methods of electronic delivery that will be used, such as text message, electronic mail or an online patient portal, to obtain the patient's verifiable affirmative consent to receive a digital copy that way, and to keep records or evidence of that consent for not less than three years, available to the Commission. An app that mails a PDF and keeps no consent record has made the practice worse off, not better.

Contact lenses carry their own rule. After a fitting the prescriber has to give the patient a copy of the contact lens prescription whether or not it was asked for, and has to confirm that the release happened: a signature on a receipt, a signature on the copy the practice keeps, or evidence of digital delivery. A request from someone acting for the patient, which in practice usually means an online seller, has to be answered within forty business hours. Those records run for at least three years too.

The design point is small and it changes the data model. A release is an event, not a file: who, when, which version of which prescription, by which method, and the consent that allowed that method. Build the release record first and the awkward question three years later answers itself. Build the PDF first and you will be reconstructing the answer out of sent mail.

16 CFR 315.3, availability of contact lens prescriptions to patients

Recall is the cycle the app is actually for

Booking is a transaction. Recall is the business. The interval belongs to the patient and is set by the clinician at the end of the appointment, so the record needs a due date written there and then, not a date a report works out a year later from an average. Store the interval, the due date and who set it, and the recall list builds itself instead of being rebuilt every month.

Two other clocks run alongside it and they are not the same clock. A prescription has an expiry date. A vision plan has a benefit year, and benefit years differ by plan, so store the reset date as a field rather than assuming everyone renews in January. A patient can be due for an examination with no benefit left, or have benefit and not be due. An app that shows only one of those two numbers generates telephone calls rather than preventing them.

Then there is the contact lens supply, the most predictable thing in the practice. Quantity supplied and wear schedule give you the date somebody runs out, and a nudge two weeks before that beats any marketing message. Sending is its own problem, with consent, quiet hours and an opt out that has to work on the first tap: the mechanics are the same as any appointment reminder app, and they are worth getting right before you send to a whole list.

What a vision clinic app should hold, and what it should not

The fields that make a vision clinic app useful are specific and unglamorous. For spectacles: sphere, cylinder, axis, add, prism and pupillary distance, with the date it was written and the date it expires. For contact lenses: brand, base curve, diameter, power and those same two dates. Then the examination date, the recall due date, the release record from the section above, and the order itself: frame, lens type, lab, status.

Order status is the quiet winner. Whether the glasses are ready is a call the front desk takes over and over, and one line in the app answers it: at the lab, expected Thursday. It costs one field and one update a day, and it is the feature patients actually notice.

Some things belong to the clinician and not to the app. Clinical notes, images and anything that reads as a diagnosis stay in the practice management system. An optician appointment app that duplicates the clinical record gives you two versions of the truth and twice the exposure. Read from the management system if it offers an interface, and otherwise let the app own only what the front desk would type once anyway.

One boundary is worth naming out loud. A patient on glaucoma drops is running a medication schedule, and reminders for that are a different build with different failure modes, closer to a medication tracking app than to a booking screen. Bolting drop reminders onto a booking app is how a missed notification turns from an inconvenience into a clinical problem.