sip · e911 · clinical handsets
Charles Trinh — VoIP Telephony, Las Vegas NV

VoIP for clinical settings: SIP architecture and failover, E911 location accuracy that actually works, handset choice for infection control, and call quality you can prove.
Architecture and failover
A single SIP registrar is a single point of failure for every call including emergencies; design for a surviving path and test it.
Keep PSTN or carrier diversity for outbound emergency calling, and verify that the fallback actually routes.
Document the dial plan; undocumented dial plans produce calls that go nowhere and nobody can explain why.
E911 is the requirement that matters
Location accuracy for emergency calls is a legal and life-safety obligation, and in a multi-building campus it is where VoIP deployments fail.
Use network-based location with per-switch or per-access-point mapping, and validate by placing test calls from real rooms.
Re-validate after every network or floor-plan change, because a moved phone with a stale location is worse than no location.
Handsets for clinical use
Infection control, drop resistance, battery life and the ability to clean with hospital-grade wipes matter more than feature lists.
Avoid softphones on shared workstations for anything clinical, because the identity becomes the workstation rather than the person.
Provide a wearable or handset option for staff who are mobile, and test coverage in stairwells and lifts.
Call quality you can prove
Measure MOS or an equivalent per call path, not by asking whether it sounded fine.
Treat jitter and loss as the enemy, and enforce QoS at every hop including wireless.
Keep a baseline per site so degradation is a comparison rather than an argument.
Recording and retention
Recording is a legal artefact with consent and retention obligations that vary by state.
Log every playback and export with the requester, and restrict playback to named roles.
Set retention by policy and enforce it in the platform.
Migration and operations
Migrate by number block and by site, keeping the old system dialable until the new one is proven.
Export call detail records before cutover, since history rarely migrates cleanly.
Monitor by placing real test calls on a schedule from outside the estate.
How I do it
One trace of a real case with timestamps at every hop, before any document is written.
A findings list naming the defect, the system, the owner and the date, reviewed monthly.
No attestation I did not test, and no template sold as an assessment.
Location accuracy is the whole deployment
Emergency calling from a multi-floor, multi-building campus is where VoIP projects fail, because the dispatcher needs a specific location and the platform knows an IP address. Every method of fixing that has a cost and a failure mode: switch-port mapping needs the port to be correctly patched, access-point mapping needs the wireless to be current, and manual registration depends on people moving phones and telling somebody. Choose the method that matches how the estate changes, and validate it by calling from rooms on different floors and confirming what the dispatcher sees.
Re-validation after every move is the part nobody budgets for, and it is the part that determines whether the location is right in two years. Make the phone move a workflow with a step that updates the location record, and audit a sample each quarter by calling from a randomly chosen room. Where the platform supports a test call to a nominated number with location readback, automate it, because an automated check that runs weekly is the only version that survives contact with a busy facilities team.
Handsets and the clinical environment
The handset is a clinical object: it gets dropped, wiped with disinfectant, dropped into a sink, and handed to a colleague mid-call. Specification should follow those conditions rather than the feature list, and the deployment should include a cleaning procedure agreed with infection control rather than assumed. Where staff carry a device, the battery life has to cover a full shift with margin, because a phone that dies at hour ten is a phone that gets left in a drawer and replaced by a personal mobile phone, which is the worst possible outcome for a clinical communication system.
Coverage inside the building matters more than coverage outside it: stairwells, lift lobbies, plant rooms and the basement corridors where staff make calls. Test with the actual handset in those places rather than with a phone on a desk, and treat a dropped call in a stairwell as a defect rather than as an accepted limitation. The same test pattern applies to the wireless network, and running them together once a quarter is the cheapest way to keep both honest.
The dial plan as documentation
An undocumented dial plan produces calls that go nowhere and nobody can explain, and the explanation is usually that a prefix was added for one site three years ago and never removed. Write the plan down as a document with the routing rules, the site prefixes, the external access codes and the exceptions, and keep it next to the configuration rather than inside it. When a user reports that a number does not connect, the first question is whether the plan says it should, and the answer should take a minute rather than an hour.
Review the plan whenever a site is added or a carrier changes, because those are the two events that make it wrong. Keep a test number per site that routes through the full path, and call it after every change. The test number is the cheapest verification in a telephony estate and it catches the majority of post-change faults before a user reports them, which is the difference between a measured deployment and a hopeful one.
Recording, and the calls you must keep
Recording obligations in a clinical contact centre are not uniform: some calls must be retained for compliance, some must be deleted on request, and some should never be recorded at all because they contain information that creates more risk than the record removes. Classify the call types, decide the obligation per type, and configure the platform so the policy is enforced rather than described. A system that records everything because it was easier is a system that holds a large volume of sensitive recordings under a retention rule nobody wrote, and the first request to delete one of them will reveal that the platform cannot.
Test the retention policy by attempting to delete a recording and confirming it disappears from every store, including any export or backup. Then test the opposite: confirm a recording that should be retained is still playable a month later from the archive. Both tests are quick and both are usually skipped, which is why the first audit or the first litigation hold is when an organisation discovers that its retention is a setting rather than a fact. Write the two test results with their dates and keep them with the recordings policy.
The phone in the treatment room
Handsets in treatment rooms need speaker mode that is intelligible and a mute that is obvious, because the common clinical call is a clinician with gloved hands talking to a colleague while the patient listens. Design the button layout for that use rather than for a desk worker, and test the speaker with a person across the room rather than at the handset. Small choices about button placement and volume defaults determine whether the device is used as intended or propped against a monitor with the speaker on and no mute available.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Where this work is delivered
Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — voip telephony, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the AI and Automation category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.