Saltar al contenido principal

Manage Patients & Data

TietAI provides a unified patient view that aggregates clinical data from all connected EHR systems into a single FHIR-based record. This guide covers finding patients, navigating the detail view, keeping data fresh, and understanding how TietAI handles patient data privacy.


Where to find patient data

From the main left navigation, click Patients. The patient list shows all individuals in your organization's FHIR store — patients who have been synced from a connected EHR or created directly via the FHIR API.

nota

The patient list only shows patients that your organization's workflows have synced. If a patient is missing, check that your EHR sync workflow has run and completed successfully. See Data freshness below.


Patient list: sorting, filtering, and searching

The patient list supports several ways to find the right patient:

Search bar — Type a patient's last name, first name, MRN (Medical Record Number), or date of birth (format: MM/DD/YYYY or YYYY-MM-DD). Results filter in real time.

Sorting — Click any column header to sort. Click again to reverse the order.

  • Name (A–Z or Z–A)
  • Date of birth (oldest first or newest first)
  • Last synced (most recently updated first — useful for finding newly added patients)

Filters — Click Filter to narrow by:

  • Status — Active, Inactive, Deceased
  • Gender
  • Age range
  • Assigned care team member
  • Data source — Filter to patients from a specific connector (e.g., only Epic patients)

Filters can be combined. Your active filters are shown as tags above the list; click the X on any tag to remove it.


Patient detail view

Click any patient row to open their detail record. The record is organized into tabs:

Demographics

Basic identifying information pulled from the FHIR Patient resource:

  • Legal name, preferred name, date of birth, age
  • Gender, biological sex, race / ethnicity
  • Address, phone number, email
  • Language preference
  • Primary care provider
  • MRN from each connected EHR (a patient may have multiple MRNs if they appear in more than one system)

Conditions

All active and historical diagnoses from the FHIR Condition resource.

  • Each condition shows the ICD-10 code and description (e.g., E11.9 — Type 2 diabetes mellitus without complications)
  • Clinical status: active, resolved, inactive
  • Onset date when recorded
  • Verification status: confirmed, unconfirmed, provisional
  • Source: which EHR the condition came from

Use the Status filter at the top of the Conditions tab to show only active conditions or include resolved ones.

Medications

Current and historical medications from the FHIR MedicationRequest resource.

  • Medication name (brand and generic)
  • Dosage, route, frequency
  • Prescriber name
  • Status: active, on-hold, stopped, completed
  • Start and end dates

Click any medication row to see the full FHIR MedicationRequest resource details.

Allergies

Documented allergies and intolerances from the FHIR AllergyIntolerance resource.

  • Substance (allergen name and code)
  • Reaction description (e.g., "anaphylaxis", "rash")
  • Severity: mild, moderate, severe
  • Recorded date and recorder
aviso

Allergy data in TietAI is read from your connected EHR and is not independently verified. Always confirm allergy status in the source EHR before acting on allergy information.

Timeline

A reverse-chronological log of all clinical events associated with this patient across all connected systems.

Event types:

  • EHR sync — A workflow pulled new data from the EHR for this patient
  • Encounter — Hospital visit or appointment (from FHIR Encounter)
  • Observation — Lab result, vital sign, or device reading
  • Workflow execution — A TietAI workflow processed data for this patient (links to the execution)
  • Note — A care team note added in TietAI
  • Message — A message sent or received via the patient communication module

Filtering the timeline:

  • Date range — Click the date range picker to narrow to a specific window
  • Event type — Use the type filter to show only encounters, only observations, etc.

Wearables

Appears only if the patient has a connected wearable or medical device. Shows the most recent readings from each connected device:

  • Last glucose reading (CGM devices)
  • Last blood pressure reading
  • Last heart rate or ECG
  • Step count and sleep data

Each reading shows the value, unit, device name, and timestamp. Click View all readings to see the full history for a device. All readings are stored as FHIR Observation resources.


Accessing a patient from a workflow execution

When you open a workflow execution that processed patient data, each record in the execution output links to the patient's TietAI record. Click the patient name in the execution output panel to open their detail view directly.


Data freshness

The patient record shows a Last synced timestamp at the top right of the detail view, indicating when TietAI last pulled updated data from the connected EHR.

How sync works: Patient data is updated by your EHR sync workflow. The sync frequency depends on how that workflow is scheduled:

  • Continuous (every few minutes)
  • Scheduled (e.g., nightly at 2:00 AM)
  • Manual only

To trigger a manual sync for a specific patient:

  1. Open the patient's detail view
  2. Click Sync Now in the top-right corner (available to Clinicians and Admins)
  3. TietAI runs the EHR fetch pipeline for that patient and refreshes the record

To check when your sync last ran:

  1. Go to Hydra Builder → Workflows
  2. Find your EHR sync pipeline
  3. The Executions column shows the last run time and status

Data privacy

All patient data is stored in your organization's isolated FHIR store. TietAI enforces strict multi-tenant isolation — patient records in your organization cannot be accessed by users in other organizations, even when hosted on shared infrastructure.

Patient data is:

  • Encrypted at rest using AES-256
  • Encrypted in transit using TLS 1.3
  • Access-logged — every patient record view is recorded in the audit log

For data retention settings, HIPAA BAA arrangements, and additional compliance details, see Administration.


Exporting patient data

From the patient record:

  1. Open the patient's detail view
  2. Click Export in the top-right corner
  3. Choose format:
    • FHIR Bundle (JSON) — Full clinical record in FHIR R4 format, suitable for system integrations
    • Clinical Summary (PDF) — Human-readable summary of demographics, conditions, medications, and allergies

Bulk export via workflow: Use the FHIR Export node in a workflow to export a set of patients programmatically as FHIR bundles. This is the recommended approach for large-scale data migrations.

nota

Exports are subject to your organization's data retention and access control policies. If the Export button is not visible, your administrator may have restricted export permissions for your role.