1. Validate the source encoding FIRST (critical root cause):

   1. Check MSH-18 (HL7 character set): Use ISO-8859-1 (LATIN-1) (native for Spanish characters ñ/á) or UTF-8; never leave it blank.

   2. Check XML prolog: <?xml version="1.0" encoding="UTF-8"?>

   3. Check SOAP/REST headers: Content-Type: text/xml; charset=UTF-8

2. Enforce explicit encoding (disable auto-detection):

   1. HL7 TCP Services/Operations: Set CharSet=UTF-8 in the config.

   2. XML transformations: Use %XML.Reader/Writer with OutputEncoding=UTF-8 in DTL/data conversions.

3. Debug natively in HealthShare (fastest tool):

   1. Use the Message Viewer to inspect raw message bytes.

   2. Test encoding with IRIS terminal: WRITE $ZCONVERT("ñá","O","UTF8") / $ZCONVERT("ñá","O","LATIN1")

4. Fix 2020.1 pitfall:

   1. Do NOT mix encodings; standardize on UTF-8 end-to-end for all interfaces (HL7/SOAP/REST/TCP).

This workflow instantly resolves corrupted special characters in HL7↔XML transformations.

Insightful AI observability solution for IRIS!