Business Associate Agreements
LifelineIQ enters into BAAs with clients when the services involve protected health information. The agreement is reviewed as part of contracting.
Security, integrations, and implementation
The questions that should be answered before contracting.
A product demonstration is only one part of evaluation. This page explains the current public facts and the details we put into a written agency scope.
01
Security review
BAA, safeguards, authentication, access boundaries, and auditability.
02
Technical fit
Source systems, integration direction, mapping, and exception ownership.
03
Implementation
Configuration, migration, validation, training, rollout, and support.
04
Commercial clarity
Included modules, prerequisites, availability, data terms, and responsibilities.
PHI safeguards
Security is part of the operating model.
These are production controls described in the current privacy and engineering standards. Current supporting documents are shared directly during a qualified review.
Encryption
Protected data is encrypted at rest with AES-256 controls and in transit with TLS 1.2 or newer across the production environment.
Access and authentication
Role-based access, tenant and agency boundaries, multi-factor authentication, and fail-closed authorization protect access to operational and clinical records.
Auditability
Sensitive access and administrative actions are audit logged. Security and PHI-related audit records follow documented retention requirements.
Independent assurance
Ask for the current audit, certification, penetration-test, and security-document status during evaluation. LifelineIQ does not present a planned or expired assurance document as a current certification.
Integration fit
Name the source, direction, and owner.
A brand name alone does not prove compatibility. Before contracting, the scope should identify the exact system, data direction, fields, frequency, error handling, and responsible owner.
NEMSIS and ePCR
NEMSIS ingestion, validation, submission, and ePCR integration workflows support the clinical record entering and leaving LifelineIQ.
CAD and secure data intake
CAD webhooks, secure file transfer, and mapped data feeds support operational records that originate outside the platform.
Clearinghouse and payments
Waystar clearinghouse workflows, EDI activity, remittance processing, and Stripe payment workflows are available within the revenue architecture.
Operational partners
Selected connectors support identity, recruiting, background screening, finance, communications, and transportation workflows. Availability depends on agency configuration.
Implementation
A rollout plan built around readiness.
Implementation timing depends on module scope, source-system access, migration volume, integration work, and agency availability. After discovery, the agency receives a written target plan rather than a generic promise.
01
Discover
Document current systems, owners, data sources, handoffs, risks, and the first useful outcome.
02
Scope
Confirm included modules, integration direction, migration boundaries, dependencies, and acceptance criteria.
03
Configure
Set up the agency, permissions, workflows, billing rules, integrations, and role-specific workspaces.
04
Validate
Use non-production records to test mappings, access, workflows, exceptions, and operational readiness.
05
Train
Prepare administrators and role-based rollout groups with guided setup, documentation, and first-task checklists.
06
Go live
Complete readiness signoff, establish the first-week support window, and phase access around agency capacity.
Module availability
Put the exact scope in writing.
The public product pages show current LifelineIQ interfaces with fictional training-agency records. Role access, configuration, integrations, and deployment sequence still vary by agency.
Included
Modules and workflows included in the proposed scope.
Requires configuration
Capabilities that need agency rules, data, permissions, or integration work.
Sequenced later
Current capabilities intentionally held for a later rollout phase.
Customer references
Qualified buyers can request the current reference process and available agency conversations.
Data terms
Ownership, permitted use, retention, export, and transition obligations should be reviewed in the governing agreement.
Support
The implementation scope identifies training, go-live support, ongoing support channels, and ownership after handoff.
Bring your security and implementation checklist.
We will answer what is true today, identify what requires agency-specific scoping, and document open questions before a proposal.