Continuous care intelligence between clinical encounters.
Life Care System™ organizes longitudinal patient information from a defined clinical baseline through continuous monitoring, clinical change, clinician response, encounters and utilization, and measurable outcomes.
Two Primary Care Pathways
LCS uses the same longitudinal intelligence engine while preserving the clinical purpose of each monitoring episode.
Discharge to Encounter & 90-Day Outcome
Discharge Baseline → Continuous Monitoring → Clinical Change → Physician Response → Encounter / Utilization → Outcome
Supports surveillance between discharge and subsequent encounters, with special emphasis on potentially avoidable readmission, emergency-department utilization, and unscheduled acute-care utilization during the first 90 days.
Clinical Baseline to Ongoing Outcome
Clinical Baseline → Continuous Monitoring → Clinical Change → Physician Response → Encounter / Utilization → Outcome
Supports longitudinal monitoring between outpatient encounters, including physician-defined baselines following evaluation, treatment or medication change, procedure, diagnostic event, or another clinically selected point.
LCS Longitudinal Care Model
One care-intelligence architecture connects patient-generated information, clinician action, utilization, and outcome over time.
Population Intelligence
Database-driven monitoring across authorized patients and care pathways.
LCS Setup
Create the organization, authorized personnel, and patient records used throughout Daily Check-In, the Clinical Dashboard, and Reports.
Organization Setup
LCS Demonstration Health Network
Life Care System™ Patient App
Daily Check-In
Your secure daily connection to your care team.
Privacy, Consent & Permissions
Please review and acknowledge each item before entering the Life Care System™ Daily Check-In demonstration.
Open Demonstration Privacy Notice
Purpose of this notice
This demonstration explains how information entered into Life Care System™ may be collected, used, protected, and made available within a contracting organization’s authorized care process. The contracting organization—not the patient—must supply or approve the final production notice, effective date, privacy contact, and applicable legal language.
Information the system may collect
Depending on the patient’s approved monitoring plan, LCS may collect identifiers, baseline information, weight, blood pressure, pulse, medication-plan completion, activity, nutrition indicators, breathing, swelling, overall condition, patient notes, clinical responses, encounters, utilization, and longitudinal outcomes.
How information may be used
- To organize Daily Check-In information for authorized review.
- To compare ongoing observations with the applicable clinical baseline.
- To support the contracting organization’s clinical workflow, response documentation, quality improvement, operations, and authorized reporting.
- To maintain a continuing longitudinal record according to the organization’s policies and applicable requirements.
Who may have access
Access is limited to the patient and authorized personnel designated by the contracting organization according to their roles. Theron Global/LCS personnel do not routinely enter or manage patient data. Exceptional technical-support access should occur only when authorized to resolve a defined issue and should be restricted and audited.
Information sharing
Information may be made available to the patient’s approved physician and care team and otherwise used or disclosed as permitted or required by the contracting organization’s final notice, authorizations, agreements, policies, and applicable law. Separate authorization may be required for uses not otherwise permitted.
Patient rights and questions
The final production notice should explain how a patient may request access, request a correction, obtain a copy, request restrictions or confidential communications where applicable, receive information about certain disclosures, withdraw applicable authorizations, and raise a privacy concern without retaliation. It must identify the contracting organization’s privacy contact and explain applicable complaint options.
Security and limitations
Production access requires individual authentication, role-based permissions, secure transmission and storage, audit controls, and organizational safeguards. Daily Check-In is not an emergency service and does not independently diagnose, prescribe, or change treatment. Patients should follow the contracting organization’s emergency instructions.
Demonstration restriction
Do not enter real patient or health information into this demonstration. No demonstration acknowledgment, signature, permission, or check-in is intended to be saved or transmitted.
Your Assigned Clinical Team
Loading assigned physician…
No additional care-team members are currently listed.
Loading organization…
Today's Check-In
How are you feeling?
What I am tracking today
Use the measurement routine established by your clinical team. The physician interprets the pattern.
Report whether the prescribed plan was followed. LCS does not independently change medication.
Complete only physician-approved activity and report how you felt. New or concerning symptoms require appropriate clinical or emergency evaluation.
Record the simple high-salt-meal indicator rather than trying to calculate exact dietary sodium.
Consent & Privacy Center
View the status of notices, consents, authorizations and communication preferences associated with your LCS record.
Longitudinal Clinical Dashboard
Enter the demonstration PIN to access longitudinal clinical intelligence across Post-Discharge and Outpatient care pathways, Clinical Response, encounters/utilization, and outcome reporting.
Life Care System Subscriptions
Institutional and population-based access to longitudinal patient support, clinician intelligence, reporting and compliance infrastructure.
Practice Subscription
For authorized physician practices and clinical teams managing a defined patient population.
- Patient Portal
- Longitudinal History Files
- Clinical Results Desk
- 30/60/90-day, 6-month, 12-month and all-history reports
Organization Subscription
For hospitals, health organizations, municipalities and sponsored programs requiring multiple professional users.
- Organization administration
- Role-based access architecture
- Population dashboards
- Compliance & audit administration
Enterprise / Population
For larger populations, payer programs, health systems and custom deployments requiring integration and governance design.
- Custom population configuration
- Integration planning
- Advanced reporting
- Enterprise governance
LCS Production Activation Center
This center separates the working demonstration from the controls required before real protected health information or paid subscriptions are activated.
Identity, Data, Consent, Audit & Subscription Foundation
The LCS build now includes a vendor-neutral production data model and protected API gates. Patient, clinician, supervisor, organization administrator and system administrator roles are defined; longitudinal check-ins, clinical responses, versioned consent records, audit events and organization subscriptions have dedicated data structures.
Activation Gates
| Gate | Requirement | Current State |
|---|---|---|
| Secure Identity | Production authentication, professional MFA, role assignments and session controls. | Not connected |
| Protected Data Store | Persistent database with encryption, backups, retention and documented recovery. | Not connected |
| Clinical Governance | Consent/authorization versioning, minimum-necessary access, audit and amendment history. | Workflow defined |
| Vendor/BAA Review | Determine covered-entity/business-associate roles and execute required agreements before PHI. | Required |
| Commercial Activation | Final subscription terms, organization onboarding, payment and account provisioning. | Not connected |
System Status
The application now exposes a non-PHI system-status endpoint so the production environment can report whether protected data, billing and authentication are enabled.
Privacy, Consent, Security & Compliance Center
Administrative architecture for protecting longitudinal patient information and governing authorized access.
Compliance Administration
| Control Area | LCS Production Requirement | Status |
|---|---|---|
| Identity & Authentication | Individual accounts, MFA for professional users, secure sessions and account lifecycle management. | ${'Pending production backend'} |
| Access Control | Minimum-necessary, role-based permissions and controlled emergency access procedures. | Architecture defined |
| Audit Logging | Tamper-resistant record of access, creation, changes, exports and administrative activity. | Architecture defined |
| Encryption | Production controls for ePHI in transit and at rest based on security architecture and risk analysis. | Pending production backend |
| Consent & Authorization | Versioned notices, consents, authorizations, signatures, revocation and change history. | Workflow designed |
| Backup & Recovery | Documented backup, recovery, retention and secure disposal program. | Pending infrastructure |
| Incident & Breach Response | Detection, escalation, documentation, risk assessment and notification workflow. | Workflow designed |
| Business Associates | Vendor inventory and BAAs where legally required. | Required before PHI |
Longitudinal Record Governance
Every enrolled patient receives one continuing history file. Reporting windows are views into the history, not separate records.