Field notes for your next visit
Why appointment topics and connection permissions are separate
See how VisitQuill separates authorized record access from the talking points a visitor selects for an appointment brief.
Two choices with different effects
Approving a record connection determines which categories the application may receive. Checking a talking point determines which returned label goes into the appointment brief. These are separate controls: unchecking a topic is not a request to revoke sharing.
Keep the connection on the server
The source implementation starts a hosted connection through a separate server. That server requests the categories allowed for VisitQuill and returns to this site’s import workspace. Browser code does not contain the production API key. The visitor’s temporary session is bound to the exact site origin.
Keep the discussion list in the product
Once records are available, the interface maintains a selection of record IDs and derives the brief from those IDs. That makes the output inspectable: every talking point should correspond to a selected entry. The interface does not add recommendations, decide which condition is most important, or send the list elsewhere.
Make the boundary visible at handoff
A future operator should preserve this separation when extending VisitQuill. Adding a question editor need not broaden record access. Adding a new record category does require reviewing the actual authorization request and disclosures. The current public deployment documents the implemented flow; it is not evidence that a patient connection has been activated.
The role of FinchNode in this design
In VisitQuill’s implementation, FinchNode supplies the authorization handoff and records the server can request. VisitQuill supplies the appointment-specific selection and text output. The distinction keeps the explanation of the brief tied to what the visitor actually chose.
Questions about this guide
Does removing a talking point revoke access?
No. It changes the brief selection. Use the sharing controls described in the privacy notice to manage the authorized connection.