Aparavi DTC icon

Aparavi DTC

Complete Aparavi DTC platform with OCR, parsing, transcription, PII censoring, and custom pipelines
Join our community

Actions10

Overview

This node integrates with the Aparavi DTC platform to perform various data processing operations including OCR, document parsing, audio transcription, audio summarization, PII anonymization, advanced parsing, and PII censoring specifically for healthcare data under HIPAA regulations. It supports processing input from file paths, binary data, or text data and can handle custom pipelines as well. The node is useful for automating data extraction, transcription, and sensitive data redaction in workflows, especially in healthcare compliance scenarios.

Use Case Examples

  1. Automatically censor healthcare-related PII in patient records to comply with HIPAA.
  2. Extract text from scanned medical documents using OCR for digital archiving.
  3. Transcribe and summarize audio recordings of medical consultations.
  4. Run custom Aparavi pipelines for specialized document processing.

Properties

Name Meaning
Input Type Specifies the type of input data to process: file path, binary data, or text data.
File Path Full path to the file to process (shown when Input Type is 'File Path').
Binary Property Name of the binary property containing the file to process (shown when Input Type is 'Binary Data').
Text Data Text data to process (shown when Input Type is 'Text Data').
Input Data Mode Determines whether to process all fields or only specific fields in the input data (for PII censor operations).
Fields to Process Comma-separated list of field names to process (shown when Input Data Mode is 'Specific Fields').
Censor Character Character used to censor detected PII.
Options Additional options including custom API base URL, timeout in seconds, and retry attempts on failure.

Output

JSON

  • json - Contains the processed result from the Aparavi platform, such as censored text, parsed data, transcriptions, or pipeline execution status.

Dependencies

  • aparavi-client npm package for API interaction

Troubleshooting

  • Ensure valid Aparavi API credentials are provided; missing API key will cause operation failure.
  • File input requires valid file paths accessible by the node environment.
  • Binary input requires correct binary property name and valid binary data from previous nodes.
  • Text input is only supported for specific operations like PII anonymization; using text input for unsupported operations will cause errors.
  • Invalid JSON format for custom pipeline configuration will cause parsing errors.
  • Network connection issues to the Aparavi API may cause retries or failures; check connectivity and API endpoint URL.

Links

Discussion