The waveform is clean.
The report header is not.
AliveCor, Cardiologs, and idoven want your ECG dataset. Your patients' names, DOBs, and referring clinician details are in every SCP-ECG and HL7 aECG header. CardioIQ strips all of it inline - before any study reaches an AI vendor, a research archive, or a registrar's inbox.
Before and after CardioIQ.
Everything standing between your cardiology department and an AI ECG or echo vendor partnership.
Cardiology data is richer than imaging.
The PHI surface is too.
A single cath lab report may contain patient name, DOB, referring clinician, procedural notes with incidental identifiers, and embedded PDF attachments. Standard DICOM export tools address the header. Nothing else. CardioIQ processes every surface.
The CardioIQ pipeline.
Three things that change immediately.
Connected to your ECG system
We configure CardioIQ between your ECG machines and the downstream destination - GE MUSE, Philips, Siemens, or direct EMR export. Half-day engagement, no workflow changes.
AI vendor receives clean data
AliveCor, Cardiologs, or your research partner gets waveforms with all identity removed. The clinical signal - intervals, rate, morphology - is intact and usable.
Audit trail for every study
Every ECG, echo, and cath report that moves generates a signed log entry. Ready for HREC submission, institutional governance review, or TGA audit from day one.
What CardioIQ covers.
Signal-preserving de-identification
CardioIQ separates the clinical signal from the patient identity - every time. Waveform data, measurements, and diagnostic metadata are preserved intact. Every piece of patient-identifiable information is stripped, pseudonymised, or redacted based on your configured profile. The output is clinically valid and identity-free.
Report text de-id
Intelligent de-identification strips names, dates, and incidental identifiers from structured and free-text cath lab reports.
Embedded PDF handling
PDF attachments inside study objects processed - not skipped. Clinician references and letterheads removed.
Policy-gated routing
AI vendor and research archive access governed per data-use agreement. Enforced at network layer.
Immutable audit chain
Every de-identification event signed and timestamped. Exportable for HREC, TGA, or institutional review.
The formats your cardiology lab actually uses.
What cardiology teams usually ask us.
AliveCor or Cardiologs wants our ECG dataset. How do we share it safely?
The blocker is always the header. SCP-ECG, HL7 aECG, and GE MUSE files carry patient name, DOB, and referring physician in structured header fields. CardioIQ strips those fields inline before any file moves to an AI vendor. AliveCor or Cardiologs receives clean waveforms - the clinical signal is intact, the patient is not identifiable.
Our ECG machine export already strips the patient name. Isn't that enough?
For the name field, yes. For the rest of the header, typically not. Referring physician, ordering clinician, DOB, acquisition time, and free-text diagnostic notes are carried in fields that basic export settings do not address. CardioIQ processes every PHI-bearing field per a configurable de-identification profile - not just the name.
What about the referring clinician's name and free-text notes in a cath lab report?
That is one of the surfaces most commonly missed. Cath lab reports may contain referring physician name, procedural notes with incidental patient identifiers, and embedded PDF attachments with letterheads. CardioIQ processes free-text report content and embedded PDFs - not just the structured metadata.
Does CardioIQ work with our GE MUSE, Philips, or Siemens Healthineers system?
Yes. CardioIQ supports SCP-ECG (GE MUSE, Siemens), HL7 aECG (Philips XML), DICOM Waveform, and standard echo SR formats. Integration is configured per your device and output format. No changes to your ECG acquisition workflow.
What do we need to demonstrate to HREC for a cardiac AI research project?
Most HRECs will want a documented de-identification methodology, an audit trail of data movements, and alignment with OAIC APP 11 and DICOM PS3.15. CardioIQ generates a signed methodology manifest for every release - format, version, fields processed, audit hash. Designed to be attached directly to an HREC ethics variation or data governance submission.
How does CardioIQ handle echo studies, ECGs, and cath reports differently?
Each modality has a distinct PHI surface. ECG headers carry structured demographic fields. Echo studies contain DICOM SR documents with embedded reports. Cath reports carry free-text procedural notes and PDF attachments. CardioIQ applies the correct processing pipeline to each format - you do not need to manage separate tools for different cardiology modalities.