Closed jarzombekdavid closed 4 years ago
Hi @jarzombekdavid, I actually think the package is right: your OBR_31 field is of type CE, which should have 6 components, according to specification, while your messages have 7 components, so validation fails.
PS: Validation is always performed with STRICT level. You can parse a message using TOLERANT level but validation is performed against the official structures using STRICT policy. We implemented a TOLERANT level since we are aware that the real world doesn't always conform to specification (sic!)
Ah ok that makes sense I miss-understood. I thought validation had different levels itself but that totally makes sense in terms of it just allowing the message to be parsed.
Running on python 3.6 and hl7apy version 1.3.3
I'm having issue with message validation for ORU^R01. I am running the below code for the below hl7messages. I believe they are valid though with fake data and I keep getting the below validation issues. Is this expected behavior? I've tried both STRICT and TOLERANT validation levels. I've also tried this on real hl7 messages omitted due to the inclusion of phi but I get the same problems.