cameras · retention · privacy
Charles Trinh — IP Surveillance and CCTV, Las Vegas NV

IP video surveillance in healthcare: coverage design, retention and access policy, bandwidth and storage sizing, and the privacy obligations that govern recording patients.
Coverage by purpose, not by count
Define what each camera is for: perimeter, pharmacy, cash handling, corridor safety, or controlled drug storage.
Every camera should map to a purpose and an owner; coverage without a purpose attracts privacy complaints and provides no evidence.
Never cover treatment areas; the clinical record is the record, and video adds liability rather than proof.
Retention and access
Retention follows the purpose and the law, and access to footage must be logged with a requester and a reason.
Treat footage as sensitive data: encrypted storage, restricted playback, and an export log that survives audit.
Publish an internal retention schedule and enforce it in the recorder rather than in a policy document.
Bandwidth and storage sizing
Sizing is arithmetic: resolution, frame rate, scene complexity, retention days, plus a margin for simultaneous playback.
Use motion-based recording where the purpose allows, and continuous where evidence requires it, and say which in the design.
Plan storage growth as cameras are added, because retrofitting storage is an outage.
Network and hardening
Cameras are the least-patched devices on most networks; isolate them, block outbound internet, and disable vendor cloud features unless required and reviewed.
Change default credentials on every device, including the ones the installer said were already done.
Keep firmware current where the vendor supports it and record where they do not.
Evidence handling
Chain of custody, hashing on export, and a documented process for law enforcement requests.
A clip exported without a hash and a log is an allegation rather than evidence.
Name the person who authorises release, and record the authorisation.
Operations
Monitor camera health and recording status, because a camera that stopped recording three weeks ago looks identical to one that is working.
Alert on storage failure and on tamper events, and test the alert path quarterly.
Keep an as-built camera map with identifiers that match the recorder.
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.
The privacy assessment comes first
Recording patients is a processing activity with legal consequences, and the assessment that determines whether each camera is permissible should be written before the camera is purchased rather than after a complaint. It should name the purpose, the area covered, the retention, who may view and how access is logged, and it should be signed by someone who owns the risk rather than by the integrator. An estate with sixty cameras and no assessments has sixty unexamined practices, and the ones that will be found first are the ones covering a queue at a pharmacy counter.
Where the assessment concludes that a camera is not justified, remove it or reposition it, and record the decision. The instinct when a camera becomes contentious is to add signage or a policy; neither changes the fact of the recording, and the assessment is the artefact that demonstrates the organisation thought about it. Review the assessments when the building changes, because a consultation room converted from a storage room changes the character of a camera that has not moved at all.
Storage, evidence and the export chain
Footage becomes evidence the moment somebody asks for it, and the quality of the export determines whether it is useful: the right time window, the right resolution, the right camera and a hash that shows the file has not been altered since. Build the export procedure before the first request, test it with a dummy, and keep the log of who exported what and why. An export produced by screen-recording a playback window is not evidence, and it is the most common thing an organisation hands to a police officer because nobody built the proper path.
Retention should be enforced by the recorder rather than by a policy, and the retention period should be the one in the assessment rather than the default the installer configured. Where a longer retention is required for a specific investigation, extend it for the specific cameras and record the authorisation, rather than extending the whole estate. That distinction keeps the general retention short, which is both the lawful position and the one that reduces the cost of the storage you need to size.
Keeping the system working
A surveillance system fails quietly: a camera whose recording stopped three weeks ago displays a live image in the client, so the operator sees a working camera and the recorder shows a gap only when someone looks for it. Monitor recording status per camera, alert on any gap over a few hours, and test the alert by deliberately disabling a camera. The same monitoring should cover storage headroom and the age of the oldest recording, because both tell you whether the retention promise is being kept.
Patch the recorders and the cameras where the vendor supports it, and record where they do not, because a camera fleet is the largest concentration of unpatched embedded devices in most estates. Isolate the camera network from everything clinical, block outbound access except to the management platform, and disable the vendor's cloud convenience features unless a written decision says otherwise. These three steps take a day and remove the majority of the realistic attack surface in a surveillance estate.
The camera you did not approve
Estate managers, contractors and even well-meaning departments install cameras without telling the security team, and each one is a processing activity nobody assessed and a device nobody patched. A quarterly walk of the building, with a phone and the as-built map, finds them: a new camera above a pharmacy counter, a doorbell camera at a staff entrance, a webcam pointed at a queue. The finding is not evidence of malice; it is evidence that the organisation did not make it easy to do the right thing, which is why the response should include a simple route by which a department can request a camera and get a decision quickly.
Record the unapproved devices and the disposition of each, because the pattern tells you where the need is real. If three departments have installed cameras at their own entrances, the estate probably needs coverage there, and the assessed installation will be better than three consumer devices with unknown retention. Treating these findings as a design input rather than as a series of breaches is what makes the inventory converge towards the actual need rather than being a recurring sweep against behaviour that the estate itself has caused.
Time synchronisation and the sequence
Evidence is a sequence, and a sequence depends on every device agreeing about the time. Cameras that drift by seconds, a recorder on a different timezone and a door system on a fourth make an investigation a guess. Point every device at the same time source, set the same timezone everywhere, and check the drift quarterly against the reference clock. The check takes minutes and it is the difference between a timeline that can be presented and one that invites a challenge about which system was right.
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 — ip surveillance and cctv, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the AV and IT Infrastructure 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.