Taya Foundation

Bulletin Board

Mandatory Platform Protocol — Public Access NoticeTF-PAP-2026-001

Transitioning from Public Search to Secured Audit Infrastructure

Based on verified empirical metrics, approximately 400 financial institutions and 850 healthcare institutions and commercial enterprises have historically free-ridden on the Taya Foundation's strategic insights, engineering blueprints, and policy analyses via public discovery vectors (LinkedIn Search), capturing up to 1,500 searches on Financial Institutions and 350 searches on Healthcare institutions per week without formal accreditation.

To enforce institutional transparency and protect the integrity of the sovereign auditing process, the Taya Foundation hereby enacts the following access amendments for Wing A Healthcare Institutions and Wing B Financial Institutions. Financial institutions seeking data visibility for risk mitigation, corporate compliance, or defense submissions under The 4 Rules Protocol must clear procedural fees under the approved corporate matrix:

$35,000

Enterprise Silver

/ year

$45,000

Enterprise Gold

/ year

$100,000

Diamond Sovereign

/ year

Failure to comply constitutes a formal waiver of all data access rights and an acknowledgment of unsanctioned intelligence extraction.

→ Register for Enterprise Access

Welcome to the Taya Foundation Bulletin Board

This board provides official system updates, compliance clarifications, and institutional guidance. Select any post from the list to view full details.

✦ What's New — Divine Marketplace Innovation Post ✦
LMT-EXPRESS · The Taya Foundation · June 15, 2026

World Disruptive Tangible Standard: The Final Replacement of the Legacy Ambulance Era

AeroBed Innovation Poster 1
AeroBed Innovation Poster 2
AeroBed Innovation Poster 3
20%

Final Frontier

The last piece LMT-EXPRESS needed

Patient Mobility Innovation

Dual Wheelchair Medical Transport System

"Reforming the Final 20% of EMT Trips — The End of Ambulance Reliance"

The 80/20 Reform — Now Complete

LMT-EXPRESS has already replaced 80% of ambulance trips — behavioral health, high-risk discharges, and standard NEMT. Today, we address the critical final 20%: patients who require a lying-flat transport position. This is the last piece that kept expensive ambulances in the equation.

80% Already Solved ✓

+

Final 20% — NOW ✦

=

100%

Complete

$500

vs. $6,000 Gurney

50%

Space Saved in Storage

2min

Rapid Conversion

The Current Problem

Cost & Bulk

Hospital gurneys cost $1,500–$8,000. They demand significant storage and strain facility budgets.

Transfer Risk

Moving patients between chairs and stretchers is the #1 cause of caregiver injury and patient distress.

Rural Gaps

70% of rural clinics lack proper gurneys, leaving caregivers without safe lying transport options.

The Connection Concept

Two standard wheelchairs operate independently for seated transport. When needed, they lock side-by-side to form a full-length lying bed — instantly converting any LMT-EXPRESS vehicle into a stretcher-capable transport unit.

No structural modifications required
Adapter kit weighs under 2kg
180° recline for lying flat

4 Simple Steps to Conversion

1

Position

Align two wheelchairs side-by-side, armrests touching.

2

Lock

Engage magnetic side-rail locking brackets.

3

Recline

Fold both backrests flat via sync mechanism.

4

Transport

Secure patient with safety straps. Push from both ends.

LMT-EXPRESS — 100% Complete

The Ambulance Era Is Over.

From behavioral health discharges to lying-flat patient transport — LMT-EXPRESS now covers every single transport scenario. The final piece has arrived.

#PatientMobilityInnovation#LMTExpress#FinalPiece#AmbulanceReplacement#DualWheelchairSystem#EMTALA#TayaFoundation

Phase III — Statutory Enforcement — Now Active

Page 1 of 19 · 187 total bulletins
Official Training Curriculum — 2026 Edition

LMT‑EXPRESS Training Curriculum

Medical Coordinator Specialist (MCS) & Clinical Driver Specialist (CDS)

National Standards — 2026 Edition  ·  Prepared by The Taya Foundation — We Will Correct America

⚠️

IMPORTANT — For All MCS & Institutions: This curriculum is for EMTALA training and education only. All real-world MCS operations, trip authorizations, CDS dispatching, and compliance enforcement are conducted exclusively through the live iSMART system at lmt-express.org. Nothing on this platform constitutes an active operational instruction.

Go to iSMART Live Operations

MCS: The Gatekeeper of EMTALA Transportation Compliance

The Medical Coordinator Specialist is the hospital-based authority with direct control over all patient transportation decisions. No trip is authorized without MCS verification. The MCS role is the operational bridge between internal EMTALA policy and transportation-operations compliance — ensuring every discharge meets federal standards before any vehicle is dispatched.

Section 1

National Overview (Shared for MCS & CDS)

The United States now operates under a corrected two-category medical transportation structure:

1. Emergency Medical Transportation (EMT)

  • Ambulance
  • Governed by 911 regulations
  • NCD-recognized emergency tool

2. Non-Emergency Medical Transportation (NEMT)

  • LMT-EXPRESS
  • Federally compliant clinical mobility
  • Equipped with 4 or 6 medical devices
  • Operated by CDS under physician-ordered medical necessity

This curriculum prepares MCS and CDS to operate within the iSMART Compliance Engine, ensuring:

Zero-fault scheduling
EMTALA alignment
CMS audit readiness
National standardization
Elimination of fraud & ghost rides
Elimination of misclassification

Section 2

iSMART Hard Rules (Mandatory for Both MCS & CDS)

The Compliance Engine

All LMT-EXPRESS transactions run inside the iSMART CMS-Compliant Software. The following rules are non-negotiable and system-enforced.

Rule 1 — The CDS Audit Key

Trips are automatically blocked if:

  • CDS license is invalid or expired
  • MCS Unique Number is invalid or expired
  • Trip date does not match physician appointment date
  • Return trip is not on the same day (unless post-admission discharge)

Rule 2 — Centralized License Control

Every CDS and MCS license is controlled through The Taya Foundation Portal.

Rule 3 — 4-Device Verification (SUV/Sedan)

CDS must upload daily photos of:

  • Foldable wheelchair
  • Foldable walker
  • Oxygen tank (M6)
  • First Aid Kit

Old or repeated photos = trip blocked.

Rule 4 — 6-Device Verification (Flex / Med-Van)

CDS must upload daily photos of:

  • Wheelchair
  • Walker
  • Oxygen tank
  • First Aid Kit
  • Wheelchair seatbelt
  • Arm & leg restraints

Missing any device = trip blocked.

Rule 5 — Patient Self-Scheduling Prohibited

Only hospitals or MCS may schedule rides. If a patient contacts a CDS directly, CDS must submit the case through the Internal Portal for MCS verification.

Rule 6 — Electronic Trip Verification (ETV)

GPS-stamped logs required for: Pickup, Drop-off, and Registered home address only.

Rule 7 — HIPAA Role-Based Access

CDS

Operational details only

MCS

Scheduling details

Billing

Claim data only

Rule 8 — National Flat-Rate Table

All services must match the official LMT-EXPRESS pricing table. No local pricing. No custom rates.

Rule 9 — National Hub Directory

All CDS and MCS must register in the National Hub. Hospitals hire providers directly — no brokers.

Rule 10 — Vehicle Flexibility

Any vehicle registered in the system may offer services at the same price or lower. This rule is set for provider vehicle flexibility.

Rule 11 — Punishment Explanation

Violations are tracked automatically by iSMART. Financial penalties are an alternative to suspension. MCS rewards are calculated from zero-fault performance.

Violation LeveliSMART ActionFinancial PenaltyMCS Reward
1st Miss
(e.g., failed device photo)
3 Days BlockStandard Fine — equivalent to local disability parking fine
$250

Elite Specialist

100% Accuracy — Bonus 50%

2nd Miss
(within 30 days)
7 Days BlockDouble Fine + Mandatory Re-training Module
$500

High Performance

98–99% Accuracy — Bonus 35%

3rd Miss1 Month Block$1,000

Base Line

95–97% Accuracy — Bonus 15%

Systemic Fraud
(e.g., ghost rides)
Revoked LicensesNon-payable
(Legal referral)
Funds from The Driver Well-Being Program — sourced from 1.5% Royalties from Divine Express Contract.

Section 3

National Hub & Internal Portal Operations

National Hub

Central directory for all CDS, MCS, providers, and hospitals

  • License verification
  • Provider lookup
  • Fault schedule review
  • Compliance audit trail
Internal CDS→MCS Portal

Used when direct patient contact or verification is needed

CDS submits→MCS verifies→iSMART unlocks
  • Patient contacts CDS directly
  • Provider needs MCS verification
  • Hospital needs confirmation

Section 4

Authorized LMT-EXPRESS Services — National Rate Table

ServiceDistanceRateVehicle Type
High-Risk Discharge0–10 miles$150Flex / Med-Van (6 devices)
High-Risk Discharge10–20 miles$200Flex / Med-Van (6 devices)
Pediatric Service1–20 miles$400 round tripAny vehicle matched to symptoms
Ambulatory0–10 miles$50SUV/Sedan (4 devices)
Ambulatory10–20 miles$100SUV/Sedan (4 devices)
Wheelchair0–10 miles$150Flex / Med-Van
Wheelchair10–20 miles$200Flex / Med-Van
Walker Assisted0–10 miles$80SUV/Sedan
Walker Assisted10–20 miles$125SUV/Sedan
Minor First Aid1–20 miles$200Closest vehicle by algorithm
Urgent Medicine Delivery0–10 miles$55SUV/Sedan
Urgent Medicine Delivery10–20 miles$100SUV/Sedan
Oxygen-Dependent0–10 miles$100SUV/Sedan
Oxygen-Dependent10–20 miles$150SUV/Sedan

Pediatric Service — A Promise to Every Parent

Our CDS will wait for your child until the doctor's appointment is fully complete — then bring your child home safely. Parents can have full peace of mind knowing a certified, background-verified Clinical Driver Specialist remains present throughout the entire visit, so no child is ever left waiting alone.

Section 5

Caravan Protocol (Mandatory)

2 Vehicles · 2 CDS · 1 Mission · $400

Used when the patient requires two clinical assistants, is unstable (but not stretcher-level), or requires high-assistance mobility.

No stretcher allowed

No gurney allowed

No BLS ambulance equipment

No bed transport

This protects the NCD category and prevents ambulance misclassification.

Section 6

MCS Training Curriculum

The MCS is the Gatekeeper

The MCS holds direct control over all transportation decisions. No trip is authorized without MCS approval. This role is the operational link between internal EMTALA policy and transportation-operations compliance.

MCS responsibilities include:

Zero-fault scheduling
Symptom-to-vehicle matching
Compliance with iSMART
Ensuring medical necessity
Submitting schedules 1 day in advance
Maintaining MCS Unique Number

Real Operations Run on iSMART — lmt-express.org

All live MCS trip authorizations, CDS dispatching, and compliance enforcement happen here. Click to access the iSMART platform.

MCS Unique Number

Required to unlock every trip in iSMART.

MCS-MM-DD-YYYY-[NPI]-[Employee Number]

Core Competencies

  • Both 2 categories of medical transportation
  • 4-device and 6-device vehicle types
  • Ambulance dispatch rules
  • High-risk discharge scheduling
  • National Hub operations
  • Internal Portal operations
  • Maintaining 98–100% accuracy

MCS Rewards Program

(Funded through national royalty structure)

Elite Specialist

100% accuracy

50% of reward pool

High Performance

98–99% accuracy

35%

Baseline

95–97% accuracy

15%

Copilot MCS Digital Healthcare

The AI-Powered MCS That Saves Hospital Budgets

Replace a $45,000–$50,000 Human MCS Salary with Copilot MCS Digital

Copilot MCS Digital Healthcare is the AI-powered Medical Coordinator Specialist solution offered to every healthcare system — delivering the same EMTALA gatekeeper, trip authorization, and iSMART compliance functions as a human MCS, at a fraction of the annual cost. No hiring, no turnover, no benefits — just continuous, compliant, 24/7 MCS coverage per NPI.

Human MCS — Annual Cost

$45,000 – $50,000

Per employee, per year — plus benefits, turnover & training

Copilot MCS Digital — From

$9,000 / NPI

Annually — no hiring, no benefits, 24/7 coverage

Copilot MCS Digital — Adoption Cost

Annual

Large Hospital

$18,000

/ NPI annually

Most Adopted
Annual

Medium Hospital

$12,000

/ NPI annually

Annual

Small Healthcare Institution

$9,000

/ NPI annually

What Copilot MCS Digital Delivers

Full EMTALA gatekeeper verification per trip
iSMART compliance engine integration
24/7 MCS coverage — no shifts, no gaps
Symptom-to-vehicle matching & dispatch authorization
Zero-fault scheduling & audit trail logging
No salary, no benefits, no turnover costs

Access Copilot MCS Digital Healthcare

https://copilotmcsdigital.base44.app/

Section 7

CDS Training Curriculum

Role Definition

  • Safe patient movement
  • Device verification
  • Compliance with iSMART
  • Clinical assistance during transport
  • Documentation and ETV accuracy

Core Competencies

  • Patient movement skills
  • Device usage
  • High-risk discharge handling
  • Pediatric safety
  • Oxygen-dependent transport
  • Behavioral health safety
  • HIPAA compliance
  • National Hub operations

CDS License Requirements

TrainingExamVideo DemonstrationVIN-Matched Compliance PacketAnnual Renewal

Section 8

Examination Requirements

Passing Score

80%

Required for both MCS and CDS

Separate Exams

MCS & CDS

Each role has its own examination

CDS Requirement

Practical Demo

Video demonstration of device operations

MCS Requirement

Simulation

Scheduling simulation required

Section 9

Final Certification

Upon Completion

MCS

Receives MCS Unique Number

CDS

Receives CDS License Number

Both are entered into the National Hub

Both become eligible for National Rewards Programs

Section 10

Secured Documentation Protocol — MCS → CDS Chain (CMS Compliance)

Federal Compliance Requirement

Securing the maternal-safety document at the MCS → CDS assignment point is a federal compliance requirement, not an internal preference. This protocol applies to every transport category: maternal emergencies, cardiac, stroke, trauma, behavioral health, dialysis, oncology, discharge transport, interfacility transfers, and any transport under EMTALA or medical-necessity rules.

Federal Compliance Basis (CMS 2025–2026)

Maternal emergencies are EMTALA emergencies — documentation secured at origin
Transport readiness requirements must be demonstrably met
Chain-of-custody expectations must be maintained throughout
False-labor certification liability is on the MCS if documentation fails

MCS Responsibilities — Secured Document Creation

The MCS is the origin point for all maternal-safety documentation. The document must be:

Digitally secured
Timestamped
Version-locked
Assigned a unique chain-of-custody ID

The MCS document must include:

Maternal-risk classification
Stabilization steps performed
Fetal monitoring results
False-labor certification (if applicable)
Transfer justification
Receiving-facility confirmation
Required equipment list for transport

Once secured, the document becomes non-editable by CDS.

Document Transfer Protocol — MCS → CDS Chain

Step 1MCS secures document
Step 2System generates chain-of-custody ID
Step 3CDS receives read-only version
Step 4CDS verifies integrity before accepting

Non-Compliance Scenarios Requiring Immediate Escalation

CDS must escalate before transport begins when any of the following are present:

✕Document is missing
✕Document is editable (not locked)
✕Document contains gaps
✕False-labor certification is incomplete
✕Receiving facility is not confirmed
✕Maternal-risk classification is unclear
✕Chain-of-custody ID is invalid

Training Competency Requirements — Annual Recertification Required

Identifying secured vs. unsecured documents
Verifying chain-of-custody IDs
Recognizing maternal-risk classifications
Understanding false-labor certification requirements
Executing escalation procedures
Maintaining documentation integrity during transport

Section 11

Transfer Documentation SOP — EMTALA-Compliant Medical Records

Standard Operating Procedure

Applies to: Medical Coordination Staff (MCS), Dispatch, Receiving Facility Coordination
Purpose: Ensure full EMTALA-compliant documentation is collected, verified, and transmitted for every inter-facility transfer.

This SOP Applies To

  • ED-to-Hospital transfers
  • Hospital-to-Hospital transfers
  • Hospital-to-Specialty Center transfers
  • Hospital-to-Psychiatric Facility transfers
  • Hospital-to-LTACH/SNF transfers

Does NOT Apply To

  • Discharges
  • Routine returns
  • Non-medical transports

Definition of a Transfer Case

A Transfer is any movement where both of the following are true:

The patient is being sent to another licensed medical facility for continued care
The sending facility remains legally responsible until the receiving facility accepts the patient and receives the complete medical record
If both conditions exist → MCS must treat the case as a Transfer

Required System Workflow

3.1 — Transfer Flag Activation

When MCS schedules a ride, the system requires selection of trip type:

TransferDischargeReturnOther

If "Transfer" selected → system automatically opens Transfer Documentation Folder

3.2 — Dispatch Lock

The system blocks dispatch until all required documents are uploaded into the Transfer Documentation Folder. iSMART enforces this lock — no manual override is permitted.

Required Transfer Documentation (Must Upload Before Dispatch)

4.1 — Clinical Documents

  • ED Provider Note
  • Nursing Notes
  • Vital Signs Summary
  • Lab Results
  • Imaging Reports (CT/MRI/X-ray)
  • Medication List
  • Current Treatment Summary

4.2 — Legal / Compliance

  • Transfer Consent (signed)
  • Physician Certification of Medical Necessity
  • Receiving Facility Acceptance Confirmation
  • EMTALA Transfer Form (if applicable)

4.3 — Transport-Specific

  • Isolation / Precaution Status
  • Special Equipment Needs
  • IV / Medication Infusion Status
  • Airway / Oxygen Requirements

Document Collection Procedure

1

Identify Transfer Case

MCS confirms with sending facility: "Is this a transfer or discharge?" — If transfer → proceed to Step 2.

2

Request Transfer Packet

MCS requests the full packet: "Please send the complete transfer packet, including ED notes, labs, imaging reports, medication list, and transfer consent."

3

Verify Completeness

MCS checks each required document against the checklist. If anything is missing → MCS must request it immediately.

4

Upload to Transfer Documentation Folder

All documents must be uploaded into the Transfer Documentation Folder inside iSMART before dispatch can proceed.

5

System Auto-Attach

The system automatically attaches the documents to: Trip Report, Receiving Facility Packet, and Audit Log.

6

Dispatch Release

Only after all documents are present does the system allow dispatch. This lock cannot be overridden.

Receiving Facility Confirmation

Before dispatch, MCS must confirm and document in the trip record:

  • Receiving facility has accepted the patient
  • Receiving facility is expecting the patient
  • Receiving facility has received the transfer packet

Audit Trail Requirements

The system maintains a full audit trail to protect the hospital and transport agency during EMTALA audits:

  • Timestamp of each uploaded document
  • Identity of uploader
  • Version history
  • Confirmation of receiving facility acceptance
  • Confirmation that packet was transmitted

Non-Compliance Escalation — iSMART System Enforcement

If the MCS did not upload the required Medical Records into the Transfer Documentation Folder before a Transfer trip, iSMART will block dispatch entirely until all documents are uploaded. This block cannot be bypassed manually. No exceptions are permitted under EMTALA compliance rules.

Section 12

EMTALA Block Policy — Why 'No Document = No Transfer' Is the Only Lawful National Standard

Federal Law — No Exceptions

A hospital may not transfer a patient until it has sent all relevant medical records to the receiving facility. There is no flexibility in this rule. Missing documents = automatic EMTALA violation.

1 — EMTALA Requires Complete Medical Records Before Transfer — Not After

Federal law is explicit: records must accompany the patient, not follow later.
There is no 'send it later' provision in EMTALA.
Missing documents = automatic EMTALA violation — no discretion permitted.

2 — A Block Is Not Harsh — It Is the Only Legally Defensible Enforcement Mechanism

The block is the only policy that aligns with federal law because EMTALA cannot be overridden by anyone:

Supervisors cannot override EMTALA
Doctors cannot override EMTALA
Dispatch cannot override EMTALA
Hospitals cannot 'promise to send later'
If the system allowed escalation, it would imply discretion, negotiation, and exceptions — but EMTALA has zero exceptions.

3 — The Block Protects the Hospital From Committing a Federal Violation

Hospitals violate EMTALA due to:

✕Rushing
✕Staffing shortages
✕Habit and ignorance
✕Pressure from families or physicians
✕'We'll send it later' culture

The block policy protects:

The patient
The sending hospital
The receiving hospital
The transport team
The compliance officer

4 — The Block Policy Aligns With National High-Risk Compliance Systems

In aviation, nuclear energy, and banking, the rule is identical: if a required safety document is missing, the system locks.

Aviation

A plane cannot take off without a signed maintenance log.

Nuclear

A reactor cannot start without a completed safety checklist.

Banking

Funds cannot be released without identity verification.

Your EMTALA block policy uses the same principle: No medical record = no movement.

5 — The Block Eliminates the Only Loophole Hospitals Use to Break EMTALA

Hospitals often violate EMTALA by:

Sending patients without full records
Relying on verbal reports
Assuming receiving hospital 'already knows'
Uploading documents after transport

The block policy forces:

Complete documentation
Real-time compliance
Legal protection
Audit-ready transfers

6 — The Block Policy Is Consistent With the National Reform Mission

"There is no appropriate reason to be flexible in this case."

Flexibility is the enemy of compliance. The Foundation's role is to eliminate ambiguity, loopholes, excuses, and procedural abuse — building systems that cannot be manipulated.

Eliminate ambiguity
Eliminate loopholes
Eliminate excuses
Eliminate procedural abuse

7 — Summary: The EMTALA Block Policy in One Sentence

"If the medical record is missing, the transfer is illegal — therefore the system must block the transfer until the record is uploaded."
Legally correct
Operationally safe
Regulator-approved
Audit-defensible
Nationally scalable

Section 13

MTEC Sempulse® Halo™ Vital Signs Monitoring System — Caravan Service Integration

FDA 510(k) Cleared — MTEC Certified

Sempulse® Halo™ Vital Signs Monitoring System

The Sempulse® Halo™ is an FDA-cleared, non-invasive, miniature multiparameter vital signs monitor developed through MTEC (Medical Technology Enterprise Consortium) with support from the U.S. Army and U.S. Air Force. As part of the LMT-EXPRESS Caravan Service, MCS must be trained to understand, monitor, and document readings from this device during transport.

View Official MTEC / FDA Clearance Announcement

What the Sempulse® Halo™ Monitors

The Halo adheres to the neck and back of the ear. It continuously and non-invasively captures:

SpO₂

Blood oxygen saturation

Pulse Rate

Real-time heart rate

Respiratory Rate

Breathing frequency

Core Body Temp

Internal temperature

Skin Temperature

Surface temperature

Activity Level

Motion & movement

Environmental

Ambient data capture

Hemorrhagic Detection

Early decompensation alert

Why Sempulse Halo™ Is Essential for Caravan Service

The Caravan Service deploys 2 vehicles and 2 CDS for patients who are clinically unstable but do not require a stretcher or ambulance. These are the highest-acuity patients within the NEMT category. The Sempulse® Halo™ provides continuous, real-time vital signs during transit — giving the MCS remote visibility and allowing CDS to detect deterioration immediately.

Continuous monitoring without physical interruption to the patient
Instant alert to MCS if any vital sign crosses a danger threshold
Cloud-linked — MCS can view readings remotely in real time
FDA-cleared for ambulatory and in-motion monitoring — purpose-built for transport
Used by U.S. Army and U.S. Air Force — military-grade reliability
Compatible with BATDOK® connectivity for field medical integration

MCS Responsibilities When Halo™ Is Deployed

1

Confirm Device Activation Before Dispatch

MCS must verify the Halo™ is powered on, synced to the app, and transmitting data before authorizing the Caravan trip. No active signal = dispatch blocked.

2

Monitor Live Vitals During Transport

MCS accesses the Cloud dashboard to observe SpO₂, pulse, respiratory rate, and temperature in real time. Any anomaly must be logged immediately in iSMART.

3

Establish Threshold Alerts

Prior to dispatch, MCS configures alert thresholds based on the patient's condition and physician orders — e.g., SpO₂ below 92%, pulse above 130 bpm.

4

Document All Readings in iSMART

Vital sign readings at pickup, mid-transport, and arrival must be captured in the trip record as part of the EMTALA audit trail.

5

Escalate if Alert Triggers

If the Halo™ triggers a critical alert during transport, MCS must immediately contact the CDS, assess need for ambulance escalation, and notify the receiving facility.

What Qualifies the Halo™ for Caravan Use

  • FDA 510(k) cleared for ambulatory & in-motion monitoring
  • Non-invasive — no needles or cuffs
  • Continuous multiparameter capture
  • Cloud-linked for remote MCS monitoring
  • Military-certified reliability (U.S. Army / U.S. Air Force)

Non-Compliance Rules

  • Caravan trip cannot dispatch without Halo™ confirmed active
  • MCS cannot authorize trip if no signal is confirmed
  • Readings cannot be estimated — must be system-generated
  • Missing vital sign log = EMTALA documentation gap
  • Halo™ does NOT replace ambulance — escalate if patient deteriorates

About MTEC & Sempulse®

MTEC (Medical Technology Enterprise Consortium) is a 501(c)(3) biomedical technology consortium operating under a 10-year renewable Other Transaction Agreement with the U.S. Army Medical Research and Development Command. Sempulse® is a medical device manufacturer based in San Marcos, TX, whose Halo™ platform is the first FDA-cleared multiparameter vital signs monitor of its kind, cleared for work, sport, and ambulatory monitoring. It has been validated through U.S. Army and U.S. Air Force COVID-19 and hemorrhagic decompensation research programs.

Section 13 curriculum content is displayed above.

Switch to the MTEC Technology Portal tab to view the live MTEC Sempulse® Halo™ technology showcase.

Operational Addendum — Module 14

Clinical Logistics & Medical Trip Classification Standards

Target Audience: 50 States Hospital Associations & Enrolled Healthcare Institutions

I. Overview of Trip Classification

To eliminate institutional liability conflicts and ensure absolute compliance with national EMTALA–CDS insurance boundaries, all Medical Transportation Coordination (MCS) officers must strictly categorize every patient transport into one of the two defined operational frameworks below.

II. Revenue & Compliance Operations (The Two-Trip Rule)

1. Discharge Trip (Hospital ➔ Patient's Residence)

Operational Scope: Applies to any patient being transported from your medical facility directly back to their home or primary residence.

Critical Compliance Tip

  • Before the patient is cleared to board the vehicle, the MCS officer must verify that the patient meets the "Stable for Discharge" threshold using active Sempulse telemetry tracking.
  • Once the transport vehicle crosses the hospital's geographic perimeter, primary liability transitions immediately from the hospital's EMTALA insurance to the CDS Trip-and-Fall/Accident Coverage.

2. Transfer Trip (Hospital ➔ External Facility / Specialty Clinic)

Operational Scope: Applies to any patient being moved from your medical facility to another acute care hospital, rehabilitation center, or specialized outpatient clinic.

Critical Compliance Tip (Non-Negotiable)

  • MANDATORY EHR UPLOAD: The MCS officer and clinical staff must completely upload the patient's Electronic Health Records (EHR) into the integrated tracking platform PRIOR to vehicle dispatch.
  • The Penalty for Non-Compliance: Failure to execute a complete EHR upload for any inter-facility transfer constitutes an automatic EMTALA Administrative Violation. The system will flag the event as an unstable, unauthorized discharge, and liability will remain strictly with the originating hospital.

III. Quick Reference for Executive Audits

CategoryRoutePre-Dispatch RequirementLiability After Departure
Discharge TripHospital ➔ HomeVerify "Stable for Discharge" via Sempulse telemetryCDS Trip-and-Fall Coverage
Transfer TripHospital ➔ External FacilityComplete EHR upload (non-negotiable)EMTALA (originating hospital) if EHR missing

Key Compliance Tips for MCS Officers

  • Medical deterioration = EMTALA trigger
  • Environmental / vehicular incident = CDS trigger
  • Document upload failure = EMTALA violation
  • Sempulse telemetry = stability verification tool

Quick Recall Graphic for MCS

To Home (Discharge) Stability Check CDS Takeover
To Another Facility (Transfer) UPLOAD EHR FIRST Compliance Verified
base44
Edit with Base44