MajwareMAJWARE
ERR-3 = 206ErrorTable 0357

HL7 206 — Application record locked

Code 206 means the transaction could not be performed because the target record was locked by another process. It is typically transient and the message can be retried.

When you see 206 (Error Condition Code)

Raised when the receiver could not obtain a lock on the record being updated — another user or process held it at the moment of processing.

Common causes

  • A clinician or another interface was editing the same record concurrently.
  • A long-running batch process held a lock on the record or table.
  • Two interface messages targeting the same record arrived nearly simultaneously.

How to fix it

  1. 1Retry the message after a short delay — 206 is usually transient and succeeds on retry once the lock is released.
  2. 2Configure the sending interface's retry policy (with backoff) to handle 206 automatically.
  3. 3If 206 is frequent, investigate long-held locks or contention on the receiving system with its DBA/vendor.

Example ACK message

A representative acknowledgment carrying ERR-3 = 206. Open it in the HL7 Viewer to inspect every field.

HL7 v2.x Message
1MSH||^~\&|RECEIVER|HOSP|SENDER|HOSP|20260310143540||ACK^A08^ACK|ACK00026|P|2.5.1
2MSA||AE|MSG00001|Application record locked
3ERR||||206^Application record locked^HL70357|E|||Record for MRN '123456' is locked, retry

Related codes

Frequently asked questions

Should I retry on HL7 error code 206?

Yes. Code 206 (Application record locked) is typically transient — another process held the record. Retry after a short delay, ideally via an automatic retry-with-backoff policy in your interface engine.

Debug your ACK in the viewer

Paste the ACK (or original message) and get instant segment parsing, MSA/ERR decoding, and validation. Free, client-side, no signup.

Open HL7 Message Viewer →

All HL7 error & ACK codes

Browse every acknowledgment code (Table 0008) and error condition code (Table 0357) with causes, fixes, and examples.

HL7 Error Code Reference →