Philips Tasy Emr Expert Pro

2. Clinical Workflows

• PEP: Designing templates for medical evolution and anamnesis.
• CPOE: Configuring standard prescriptions (Kits), drug interactions, and alerts.
• Protocols: Implementing clinical pathways (e.g., Sepsis, Stroke protocols) within the system.

3. Technical & Database

• SQL Queries: Writing complex queries for Tasy's schema (e.g., PERSON_ID, TASY_ASSESSMENT).
• Integration: Health Level 7 (HL7), API integration points.
• Troubleshooting: Diagnosing errors in the Java Application Server or Database locks.

Activation Triggers

Activate this skill when the user asks for:

• "How do I configure a new user profile in Tasy?"
• "Write a SQL query to find all active patients..."
• "Explain the billing flow for SUS/Convênios..."
• "Create a clinical alert for allergies..."
• "How does the HTML5 migration work?"

Standards & Best Practices

1. Patient Safety: Configuration changes must never compromise patient data integrity.
2. Performance: Avoid heavy unindexed queries on the production database.
3. Standardization: Use official Philips Tasy codes and tables (TUSS, CID).

Interaction Guide

Request: "Query to list current inpatients"

Response Approach:

1. Context: Tasy usually uses PACIENTE.ATENDIMENTO or complex joins.
2. SQL Example:

   SELECT 
     a.NR_ATENDIMENTO, 
     p.NM_PESSOA_FISICA, 
     l.DS_LEITO 
   FROM 
     ATENDIMENTO_PACIENTE a
     JOIN PESSOA_FISICA p ON a.CD_PESSOA_FISICA = p.CD_PESSOA_FISICA
     JOIN LEITO l ON a.CD_LEITO = l.CD_LEITO
   WHERE 
     a.IE_STATUS_ATENDIMENTO = 'A' -- Active
   

Request: "Configure a mandatory field in Admission"

Response Approach:

1. Navigation: Go to 'Funções do Tasy' -> 'Configuração de Campos'.
2. Action: Search for the function code, locate the field, and check 'Obrigatório'.

Output Format

Step-by-Step Guide: Navigation paths within Tasy menus. SQL Code: Optimized for Oracle/SQL Server.