Category: AI & ML
Node id: ner-extractor
Standards: HIPAA
Performs Named Entity Recognition on clinical text using a dedicated NER service or LLM fallback
What it does
- Clinical Named Entity Recognition (NER)
- Dedicated NER service integration with LLM fallback
- Configurable entity type filtering
- Entity position and confidence scoring
- Support for clinical entity types (CONDITION, MEDICATION, PROCEDURE, ANATOMY, etc.)
Use cases
- Extracting diagnoses and medications from clinical notes
- Identifying procedures and anatomical references in discharge summaries
- Building structured data from unstructured clinical text
- Pre-processing text for FHIR resource generation
Runtime
- Performance tier:
variable
Output ports
Settings
Basic
Auth
Advanced
Errors
Runtime notes
- Output shape differs by source: NER service returns the raw service response with 'source' injected; LLM fallback returns {entities, source, http_status}
- LLM fallback parses the model response as JSON; if parsing fails, entities is a raw string
- Entity types include CONDITION, MEDICATION, PROCEDURE, ANATOMY, LAB_TEST, LAB_VALUE, VITAL_SIGN, ALLERGY, SYMPTOM, DEVICE
- Requires either ner_endpoint or llm_endpoint; the node prefers the dedicated NER service when both are set
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.