Clinical data moving in and out.

Identity, time and authorization matter more than the file extension. A FHIR bundle can be ingested with a hashed patient key. Laboratory rows, device streams and imaging files are not general feeds. Imaging upload is a DICOM file a site sends, capped so one object cannot fill the disk.

What this covers

FHIR

Bundle ingest in the real-world module. Not a hospital interface certification.

Labs

Not a live laboratory feed. A person can still enter a result on a form.

Devices and wearables

Not a claimed feed.

Imaging

Upload, original retained, derivative for readers. No viewer.

eCOA

The participant portal writes into the same database. It is not a third-party eCOA vendor.

Matching

A hashed key is not a master patient index.

How a team uses it

Authorize

Who may send data is a written decision.

Load

Store provenance.

Match

A person resolves identity questions.

Reconcile

Counts are compared.

Related reading

Questions

Do you match patients across hospitals?

No master patient index is claimed.

Are device timestamps trusted blindly?

No. A person should know the clock source. The product does not invent one.

Available with limitations means the described software behavior exists. A professional service is work a person does under a separate scope. Nothing here is a certification.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.