badging · zones · door hardware

Charles Trinh — Access Control Systems, Las Vegas NV

Charles Trinh — Access Control Systems, Las Vegas NV
Charles Trinh — Access Control Systems

Physical access control: credential technology, zone design that reflects clinical risk, door hardware that fails safe for life safety, and the audit trail an incident needs.

Zones follow clinical risk

Access zones should reflect what is behind the door: pharmacy, controlled drugs, IT, maternity, behavioural health, and the perimeter.

A zone that everyone can enter is not a zone; review the membership lists quarterly with the clinical owner.

Design for the exception: the cleaner at 3 a.m., the locum on their first shift, the fire service arriving.

Life-safety rules come first

Fail-safe versus fail-secure is decided by fire code and life safety, not by security preference.

Integrate with the fire alarm so egress unlocks on alarm, and test the integration on a schedule.

Never allow a security configuration to trap a person; that is the one failure that cannot be tolerated.

Credential technology

Move to high-frequency, mutually authenticated credentials; proximity cards are clonable with a phone.

Plan the migration: readers, cards, and the awkward period where both must work.

Avoid mobile credentials until the reader fleet supports them everywhere, or you create two support paths.

Door hardware and installation

The controller is half the system; the strike, the request-to-exit sensor and the door position switch are where most faults live.

Require as-built door schedules and test every door after installation, not a sample.

Record which doors are on which controller, because a controller failure is a building event.

Audit and investigation

Log every grant, denial and forced door with the credential, the door and the time.

Retention must match the investigation window; thirty days is usually too short.

Be able to answer who was in a given zone at a given time, and test that you can before you need to.

Integration and ownership

Access control touches HR for joiners and leavers, and facilities for hardware; name one owner and one integration contract.

Automate deprovisioning from HR, because manual removal is where ex-employee access survives.

Review the audit and the exception list monthly with security and facilities together.

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.

Proving who was where

An access control system earns its cost twice: once by keeping people out, and once by being able to answer, months later, who entered a given area at a given time. The second use is the one that is usually neglected, because the report that answers it has never been built and the retention is set to whatever the installer chose. Build the query before you need it: pick a door, a time window and a person, and confirm the system can produce the answer in a form you could hand to an investigator.

Retention should be set against the investigation window rather than the storage cost, because access logs are small relative to video and the cost of a short retention is paid in an investigation that cannot be completed. Keep the logs tamper-resistant and restrict who can delete them, since the system that records presence is also the system an attacker would want to edit. Where the controller supports a syslog export, ship it somewhere the access system's own administrator cannot modify.

The door is the system

Controllers, readers and software get the attention; door hardware causes the failures. A strike that is misaligned, a request-to-exit sensor that is too sensitive, a door position switch that has drifted, and a magnetic lock that is holding a door that should not be locked are the daily reality of an access estate. Require an as-built door schedule with the model of every component, and test every door after installation rather than a sample, because the doors that fail are distributed randomly across the install and the ones that fail silently are the ones nobody uses.

Maintenance should include a physical inspection each quarter of the doors that matter most, which means the ones protecting drugs, records and network equipment rather than the main entrance. The inspection is short: does the door close and latch, does the exit request work from inside, does the alarm fire when forced, does the log record a normal entry. Four checks per door, recorded, compared to the previous quarter. The record itself is evidence that the control operates, which is what a physical security review will ask for.

Integration points that matter

Access control integrates with fire alarm for egress, with HR for joiners and leavers, and with the video system for investigation, and each integration has a failure mode that belongs in the design. The fire integration is a life-safety requirement and must be tested on a schedule with the alarm vendor present; the HR integration is what makes deprovisioning actually work; the video integration is the difference between an investigation that takes an hour and one that takes a day. Name the owner of each integration, because a system that depends on three vendors and has no owner is a system that fails when the least attentive one changes something.

Test the HR integration monthly with a synthetic joiner and leaver, and confirm that the account disappears rather than merely being disabled. Where the integration is manual, the manual step needs a named person and a weekly reconciliation report. The pattern to avoid is the deprovisioning that happens when somebody remembers, because that is the pattern that leaves an ex-employee's badge working through a weekend and becomes a finding rather than an incident.

Visitors, contractors and the gap between systems

Visitor management and contractor access are where the access control design usually leaks, because the badge system covers employees well and the visitor path is a paper log at reception. Contractors arriving for a plant room, a vendor engineer at the network rack, an inspector at a ward: each needs access that is time-bound, area-limited and visible in the same record as employee access. Where the visitor process is paper, the investigation that asks who was in the pharmacy on Tuesday cannot be answered without a search of a clipboard, which in practice means it is not answered at all.

Integrate the visitor path into the access system where the platform supports it, and where it does not, at least keep a single register that is searchable by date and location. The register should record the sponsor, the areas permitted and the time out, and the reconciliation at the end of each day should be a routine rather than a project. Estates that do this find the number of unescorted contractors drops immediately, because the sponsor is named and the checkout is visible, and the control becomes a habit rather than an audit finding.

The alarm nobody watches

Door alarms that fire hundreds of times are alarms that nobody watches, and the same applies to forced-door and held-door events. Tune the sensors so the normal pattern does not generate an event, and route the ones that remain to a person who acts on them, with a record of the action. Where a door cannot be tuned, the hardware is usually the problem rather than the policy, and the fix is a strike or a sensor rather than a change of threshold. Count the alarms per door per week and work down the list.

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 — access control systems, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the Identity and Consent 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

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.

TRINH — Charles Trinh, technology architect
TRINH

Charles Trinh

Fractional CTO/CIO and Technology Architect — Healthcare Data, Identity & Regulated Infrastructure · Las Vegas, NV

Las Vegas, Nevada · US citizen · Fractional and project engagements

(702) 559-3489 Email Charles Trinh