Connections to configure

• Appointment request channel. If requests come from a website, phone intake tool or external booking service, configure a reviewed handoff into encounters. Resolve patient and clinician before entering scheduled date and visit type. Agree how the request reaches Coordinator and how the schedule is reviewed.
• Payment processing system. If money is collected outside the practice workflow, agree how confirmed results map to the payment’s patient, amount, received date and reference. Inspect the actual confirmation before treating a pending result as received. Configure the chosen provider handoff with Billing Staff before accepting its results.
• Accounting system. If the practice maintains external books, agree how Invoiced charges and confirmed patient payments are reconciled with that ledger. Define the external document mapping and reporting date scope before sending data.
• Clinical source records. If historical notes or measurements are imported, resolve the source encounter, staff records attribution and date interpretation first. Check the metric, value and unit against the clinical source before accepting the import.

Admin agrees each connection’s owner, source identity and destination mapping with the responsible clinical or billing role. Configure and test the connection explicitly before using it for the practice cycle. Retain unresolved or uncertain source outcomes for review before retrying a write.

Limit each handoff to the required information. Billing connections should use the minimal encounter projection and service details, keeping clinical notes and observations outside the billing workflow scope. A connection must not bypass Signed consent, clinical privilege, care-team coverage or workflow validation. Rehearse ordinary and rejected commands before introducing machine-generated requests.

Use implementation to agree the pilot and billing reconciliation to inspect the recorded financial scope.