Ingest CDA Documents Without Patient Linkage for De-Identification| Patient Journey Intelligence
John Snow Labs is a healthcare AI company and the industry leader in medical language models, with 150M+ downloads of its open-source libraries and models, 500+ enterprise customers, and 30+ peer-reviewed papers. Its software runs inside your own environment, on-premises or in your private cloud, with no data movement and no external API calls. Patient Journey Intelligence is the John Snow Labs platform for secondary use of clinical data. It ingests multimodal patient data (clinical notes, PDFs, FHIR, CDA, DICOM, and structured EHR records), extracts 400+ medical entities from unstructured text, harmonizes everything to the OMOP Common Data Model, and de-identifies PHI with 99%+ accuracy. Every extracted fact carries a confidence score and a link back to the source document it came from. Learn more about Patient Journey Intelligence: https://www.johnsnowlabs.com/patient-journey-intelligence/ IN THIS VIDEO Patient Journey Intelligence ingests external CDA (Clinical Document Architecture) documents without patient or OMOP linkage and makes them available as a dataset for data curation, information extraction, or de-identification. WHY THIS WORKFLOW MATTERS CDA is what arrives from health information exchanges, referral networks, and prior-vendor archives, often in volume and often about people who are not in your OMOP database. Those documents still contain the facts a study or a de-identification job needs. Document-first ingestion makes them addressable without writing anything to the patient layer, which keeps the record clean and keeps the option to link later. WHAT THE VIDEO SHOWS - Uploading CDA documents - Configuring document-first ingestion - Validating the processed files - Creating a dataset from the external documents - Using that dataset for data curation - Running information extraction or de-identification against it WHO THIS IS FOR Integration engineers, health information exchange teams, and clinical data engineers processing CDA and C-CDA content from external sources. QUESTIONS THIS VIDEO ANSWERS - How do I ingest CDA documents into Patient Journey Intelligence? - Can I process C-CDA files without linking them to an OMOP patient? - How do I run de-identification on externally sourced CDA documents? LINKS Data integration documentation: https://www.johnsnowlabs.com/pji/data_integration/overview All tutorials: https://www.johnsnowlabs.com/pji/tutorials/overview Patient Journey Intelligence: https://www.johnsnowlabs.com/patient-journey-intelligence/ All patient data shown is synthetically generated for illustration. #CDA #ClinicalDocuments #HealthcareInteroperability