IT‑IS‑Networking
Timeline › 1997–1999

Chief Systems Engineer

StorComm, Inc. — Clinical imaging company serving hospital customers. Chief designer of the StorComm PACS platform, and architect for HIPAA-compliant hospital information management systems.

Dates provisional. Recalled rather than sourced — to be confirmed against the record.

Two roles held concurrently: Chief Systems Engineer for the full tenure, and IS Manager from November 1997 to May 1999.

As Chief Systems Engineer: chief system designer of the StorComm PACS platform for hospitals, system architect for HIPAA-compliant hospital information management systems, DICOM system architecture and design, and the data center and warehouse design underneath the processing estate.

As IS Manager: designed, specified, configured, installed and maintained the entire local estate — servers, routers, bridges, switches, modems, cabling and internet service — plus the complete internet site, Exchange 5.0 and 5.5, Proxy 2.0 logging to SQL, and SMS 1.2 across the local site and remote hospitals. Wrote the standards, the acquisition and security policies, and the disaster recovery procedures.

Writing the standards for network use, operations and security, and the disaster recovery procedures, was the first time the job was governance rather than only infrastructure — a decade before the Enterprise Security Committee charter.

WORM optical archival for regulated medical records dates from here — the first of many systems whose retention rule was a law rather than a policy.

Dates provisional. The master CV records September 1997 to August 1999; two contemporaneous resumes record November 1997 to November 1999. Needs confirming.

Projects in this period

  • StorComm PACS Platform1997–1999Chief system designer of a clinical picture archiving and communication platform for hospital customers.
  • StorComm Teleradiology Platform1997–1999Diagnostic imaging delivered to radiologists at home over ISDN and dial-up — telemedicine fifteen years before the market used the word.

Technology fingerprint

The same instrument as the technology map, run over this post alone — the 3 disciplines it touched, across the 3 years it covered, weighted the same way.

Left to right is time. Each row is one of the 3 disciplines this post touched, ordered so kindred disciplines sit next to each other rather than alphabetically — a landscape only means anything if neighboring rows belong together. Height is the work running in that domain in that year, weighted by what failure would have cost — life-safety ×3, a statutory obligation ×2.2, the estate itself ×1.5, an evaluation ×1. Every project declares which of those it was, so each ridge traces to an entry you can open and disagree with. Work that ran across an employer boundary counts here as well as on the other era it belonged to. Height and color are on the record-wide scale rather than this page’s own, so a modest estate draws a modest landscape and any two of these pages can be read against each other.