InteropSec @interopsec

I make EMR data usable. Data engineer working with FHIR, HL7 and healthcare data pipelines. Open to projects. Remote Joined October 2026

Tweets

12
Followers

0
Following

33
Likes

0

InteropSec @interopsec

5 hours ago

Your EMR has the data. Making it usable is the hard part. I'm a data engineer working with FHIR. I can help: - pull data out with Bulk FHIR - turn FHIR into clean analytics tables - map HL7 v2 and CSV feeds to FHIR I also built an offline FHIR dictionary: DMs open.

0 0 0 9 0

View Details

InteropSec @interopsec

13 hours ago

Covers R4, R4B, R5 and the HL7 Extensions Pack. Try it, break it, and tell me what's missing: DM me for the link.

0 0 0 7 0

View Details

InteropSec @interopsec

13 hours ago

4. No AI, no guessing, nothing leaves your machine. Every answer comes straight from HL7's official definitions. It runs fully offline, even as a single HTML file, so it works on locked-down or air-gapped networks too.

1 0 0 8 0

View Details

InteropSec @interopsec

13 hours ago

Working with FHIR usually means digging through spec pages to find where one field lives. So I built an offline FHIR dictionary. Ask in plain English, see R4 vs R5 changes field by field, copy working JSON and code.

0 0 0 33 0

View Details

InteropSec @interopsec

13 hours ago

1. Ask the way you think. "lab normal range" → Observation.referenceRange "insurance member id" → Coverage.subscriberId You don't need to know the resource name first.

0 0 0 1 0

View Details

InteropSec @interopsec

2 days ago

@NickpxJ honestly yes, writing it out is how i actually learn the stuff and if it helps someone later, cool

0 0 0 6 0

View Details

InteropSec @interopsec

2 days ago

Note: .rs is SMART v2 (read + search). On v1 servers it's patient/Observation.read. Also check the scope field in the token response. The server can grant less than you asked for, and your app should handle that, not crash. #FHIR #APISecurity #HealthIT

0 0 0 30 0

View Details

InteropSec @interopsec

2 days ago

Your SMART on FHIR app requests patient/*.read? That's read access to every resource type for that patient: notes, meds, labs, all of it. Request only what you use: patient/Observation.rs patient/MedicationRequest.rs Smaller scope, smaller breach.

1 0 0 35 0

View Details

InteropSec @interopsec

2 days ago

Signing a FHIR document Bundle with eSign (eMudhra or any ESP)? 1. Hash the exact JSON bytes you store. Re-serialising changes them and breaks the signature. 2. Save the result in Bundle.signature, with who and when. 3. Verify it on read, not just on write. #HL7FHIR #APISecurity