Developer Documentation

True Precision AI®

This documentation is intended for clinic IT teams or developers responsible for receiving appointment data.

Overview

True Precision AI generates structured Appointment Records when a patient successfully schedules an appointment and required intake information has been completed.

Upon creation of an Appointment Record, appointment data may be transmitted to an endpoint designated by the clinic.

This documentation describes how external systems may securely receive appointment data delivered by the True Precision AI platform.

True Precision AI provides secure data delivery only. Configuration or implementation within downstream systems is managed by the receiving organization.

Event Trigger

Data transmission occurs when:

Appointment Record Created

At this stage:

  • Appointment date and time are scheduled
  • Patient intake information has been collected
  • Appointment data is finalized within the platform

Delivery Method

Appointment data is delivered via:

HTTPS POST request

All transmissions occur over encrypted HTTPS (TLS-secured) connections.

Endpoint Requirements

The receiving organization must provide an HTTPS endpoint capable of accepting POST requests.

Example:

https://your-domain.com/tpai/appointments

Requirements:

  • HTTPS endpoint required
  • Publicly reachable URL
  • JSON request handling supported

True Precision AI does not configure or manage receiving infrastructure.

Authentication

Requests are authenticated using a shared Bearer Token.

Authorization Header

Authorization: Bearer <shared-secret-token>

The shared token is exchanged securely during setup.

The receiving endpoint should validate this token before accepting incoming data.

Payload Format

Appointment data is delivered in JSON format.

Example Payload

{
  "event": "appointment.record.created",
  "record_id": "APT-10482",
  "patient_name": "John Smith",
  "email": "john@email.com",
  "phone": "5551234567",
  "date_of_birth": "1958-02-11",
  "address": "123 Main St, Phoenix AZ",
  "appointment_date": "2026-03-01",
  "appointment_time": "10:00 AM",
  "clinic_location": "Phoenix Clinic",
  "visit_reason": "Consultation"
}

Field naming may vary slightly by deployment.

Transmission Behavior

  • Data is transmitted once when the Appointment Record is created.
  • Subsequent updates are not retransmitted automatically.
  • Receiving systems are responsible for downstream processing and storage.

Delivery Responsibility

True Precision AI responsibility includes:

  • Creation of Appointment Records
  • Secure encrypted transmission of appointment data
  • Delivery to the clinic-designated endpoint

Responsibility for all downstream handling rests with the receiving organization, including:

  • Data ingestion
  • Storage
  • Mapping
  • Internal routing
  • System connectivity

Expected Response

Receiving endpoints should return standard HTTP response codes:

Status Code Meaning
200Data received successfully
401Unauthorized
400Invalid request
500Server error

True Precision AI does not monitor or remediate downstream processing failures.

Security

All transmissions:

  • Use encrypted HTTPS transport (TLS)
  • Are initiated at clinic request
  • Contain appointment-related patient information

Responsibility for handling data after receipt rests with the receiving organization. Receiving systems are responsible for ensuring appropriate handling and compliance after delivery.

Testing

A testing endpoint may be provided prior to production activation to confirm successful receipt of appointment data.

Once validated, production endpoint delivery may be enabled.

Scope of Support

True Precision AI provides:

  • Appointment record generation
  • Secure encrypted data transmission
  • Payload specification

True Precision AI does not provide:

  • Third-party integrations
  • EMR configuration
  • System configuration
  • Data mapping services
  • Middleware implementation
  • Ongoing integration maintenance

Contact

For activation requests, delivery configuration, or technical coordination, please contact:

support@trueprecision.ai

When requesting delivery configuration, clinics may provide:

  • Endpoint URL
  • Requested activation date
  • Authorized technical contact

Related Resources

True Precision AI® · Last updated February 24, 2026