Written and maintained by CASRAI Editorial Board
Last updated
AiTmed is a physician-founded telehealth, electronic medical documentation, and clinical data exchange platform engineered to unify virtual care delivery, digital patient intake, inter-facility specialty e-referrals, and decentralized clinical research data capture. Rather than relying on monolithic legacy client-server electronic health record architectures, AiTmed combines a declarative YAML-based application development standard—NOODL (Neural Object-Oriented Dynamic Language)—with an Edge-Computing Operating System (ECOS) that performs client-side end-to-end encryption (E2EE) of Protected Health Information (PHI) prior to cloud transmission.
For health informatics architects, practice administrators, and clinical trial investigators evaluating modern telehealth platform infrastructures, this guide details AiTmed’s technical stack, cryptographic privacy model, and clinical workflow capabilities.
What Is AiTmed?
Founded by practicing clinicians and systems engineers to address fragmentation across outpatient clinics, diagnostic imaging centers, and specialty referral networks, AiTmed provides an integrated cloud and edge software ecosystem for synchronous and asynchronous medical care. The platform is structured around three foundational engineering layers:
1. The NOODL (`@noodl/core`) Declarative YAML Application Framework
Conventional healthcare software development requires maintaining separate codebases for web browsers, iOS devices, Android tablets, and desktop workstations, slowing down the deployment of new clinical forms or research questionnaires. AiTmed developed NOODL (published via open-source core libraries such as @noodl/core and noodl-ui), a YAML-stemmed declarative markup and state-management specification:
- Single-Source Clinical UI Definition: Clinical informaticists define patient intake packets, specialty SOAP templates, consent forms, and ePRO clinical trials instruments as human-readable YAML schemas specifying data bindings, conditional branching logic, and validation rules.
- Cross-Platform Runtime Execution: The NOODL runtime interpreter renders the identical YAML specification natively across web browsers, iOS, Android, and desktop environments without platform-specific recompilation.
2. Edge-Computing Operating System (ECOS)
In traditional cloud EHRs, raw patient inputs, clinical notes, and diagnostic attachments are sent to centralized application servers for processing and storage, creating single points of failure and latency bottlenecks. AiTmed’s Edge-Computing Operating System (ECOS) shifts data validation, UI state resolution, document parsing, and cryptographic operations directly onto the clinician’s or patient’s local edge device (browser or mobile client), minimizing server round-trips during live clinical encounters.
3. Client-Side End-to-End Encryption (E2EE) and Permissioned Record Sharing
To operate as a HIPAA-compliant telemedicine platform across independent medical groups that do not share a single enterprise EHR instance, AiTmed enforces cryptographic access control at the document and record level:
- Asymmetric Key Cryptography at the Edge: Clinical notes, diagnostic lab reports, imaging attachments, and e-referral packets are encrypted on the sender’s device using AES symmetric keys wrapped via the authorized recipient’s public key before the payload is committed to cloud storage.
- Zero-Knowledge Cloud Persistence: Because decryption keys remain strictly with the authenticated patient, treating physician, or authorized consulting specialist, underlying cloud storage nodes store only ciphertext blocks—preventing unauthorized third-party inspection while maintaining an immutable, time-stamped audit log of every permission grant and access event.
Core Modules of the AiTmed Clinical Ecosystem
| Platform Module | Primary Users | Clinical & Operational Capabilities |
|---|---|---|
| Virtual Waiting Room & Telemedicine | Physicians, NPs, PAs, behavioral health clinicians, and patients | Browser-based and mobile synchronous video/audio consultations, multiparty family/interpreter bridging, and screen sharing for diagnostic review. |
| Digital Intake & eConsent | Front-office staff, patients, and clinical research coordinators | NOODL-powered mobile registration, insurance card OCR capture, HIPAA Notice of Privacy Practices e-signatures, and pre-visit symptom questionnaires. |
| AI-Assisted Clinical Documentation | Outpatient and telehealth clinicians | Automated speech-to-text encounter capture, structured SOAP note generation, and ICD-10-CM / CPT coding workflow support. |
| Encrypted e-Referrals & Care Coordination | Primary care practices, surgical specialists, and imaging/lab centers | One-click cross-facility referral packets with granular decryption permissions, status tracking, and closed-loop consultation reports. |
How Is AiTmed Used in Clinical Research and Healthcare?
AiTmed’s combination of declarative YAML form generation (NOODL) and edge-encrypted data transport supports both routine ambulatory care and decentralized clinical research workflows:
- Independent Practice and Multi-Specialty Network Telehealth: Outpatient clinics use AiTmed to conduct end-to-end virtual visits—from automated SMS appointment links and pre-visit intake to live video examination, electronic prescribing, and superbill generation—without maintaining on-premises servers.
- Cross-Institution Specialty e-Referrals and Diagnostic Exchange: When a primary care physician refers a patient to an unaffiliated specialist or outpatient imaging center, AiTmed allows the referring clinic to grant time-bounded cryptographic read access to relevant chart segments and diagnostic images without relying on fax transmissions or manual CD-ROM transfers.
- Decentralized Clinical Trials (DCTs) and Longitudinal ePRO Capture: Research sponsors and academic investigators use NOODL templates to deploy electronic informed consent (eConsent), remote study visits, and longitudinal patient-reported outcome (ePRO) questionnaires on participants’ personal devices (BYOD), with every submission cryptographically signed and time-stamped at the edge to satisfy FDA 21 CFR Part 11 and HIPAA Security Rule (45 CFR § 164.312) audit trail requirements.
Frequently Asked Questions
What is AiTmed?
AiTmed is a physician-developed telehealth, clinical documentation, and medical data exchange platform built on the YAML-based NOODL application framework and an Edge-Computing Operating System (ECOS). It provides end-to-end encrypted (E2EE) virtual consultations, digital patient intake, AI-assisted charting, and permissioned inter-facility e-referrals.
How is AiTmed used in clinical research and healthcare?
In healthcare and clinical research, AiTmed is used by outpatient practices, specialty networks, and clinical trial teams to conduct HIPAA-compliant video telemedicine visits, collect mobile digital intake and eConsent forms, exchange encrypted e-referrals across independent facilities, and capture time-stamped electronic patient-reported outcomes (ePRO) for decentralized clinical studies.
