Tasy API: how integration works and how to use it with AI agents
Tasy, Philips's hospital management system, is usually integrated through interfaces defined during implementation, such as healthcare standards (for example HL7) and services released by the vendor. There is no open, self-service API. Hospitals and clinics that need to connect Tasy to scheduling, laboratories and care channels use it.
What the Tasy API offers
Scheduling
Time slots, bookings and confirmations for appointments and exams, depending on the interfaces released.
Patient registration
Registration data used in scheduling and care.
Encounters
Admission and progress information for a patient's care.
Insurance billing
Account and claim data for billing.
Lab and imaging integration
Exchange of orders and results with partner systems.
How to access the Tasy API
- For partners and customersAccess is defined between the hospital, Philips and the IT team, with credentials and interfaces released for each integration. Confirm the format with Philips and the hospital's IT.
- Health data is sensitive under data-protection law (such as GDPR or HIPAA, depending on where you operate): legal basis, minimum necessary and audit.
- The agent should make no clinical decisions.
- Integrations depend on certification with the vendor and IT.
What an iTeam agent does with the Tasy API
Appointment confirmation
The agent sends the confirmation on WhatsApp, understands the reply and records confirmations and cancellations through the released interface.
Exam preparation instructions
After booking, the agent sends the exam instructions and answers the most common questions.
Billing gaps
The agent flags accounts with missing documents or authorizations before they are sent to the insurer.
Rescheduling queue
When a doctor cancels their schedule, the agent contacts the patients and offers new times for reception to confirm.
From the credential to the agent at work, with approval
Define the interface with IT and Philips
Agree with the hospital's IT and Philips which data and services will be released for the integration.
Keep credentials in the vault
Credentials stay in the iTeam vault, with agents that access only the minimum needed for each process.
Clinical validation
Validate the flows with the clinical and administrative teams, keeping human approval on sensitive actions.
Ready-made AI teams for this work
Questions about the Tasy API
Does Tasy have an API, and is it free?
Tasy has no open, self-service API. Integrations depend on your hospital's contract with Philips and often involve release of interfaces and sometimes contracted services.
Do I need to write code to use Tasy with iTeam?
Not necessarily. Once the interfaces are released, the iTeam deployment team sets up the integration together with the hospital's IT.
Does the agent access medical records?
Only if it is part of the process and authorized. For scheduling and confirmation, we recommend accessing administrative data only.
