FHIR Chat · Validator error? · implementers

Stream: implementers

Topic: Validator error?

Eric Haas (Jul 22 2019 at 18:01):

I'm not certain if here or conformance or implementers is the best place to post these issues. I assume the IG validator is the same as the core validator so I will start here.

Eric Haas (Jul 22 2019 at 18:03):

1) AllergyIntolerance The clinical status can be absent if verification status is 'entered in error'. based on this invariant:

ait-1 Rule AllergyIntolerance.clinicalStatus SHALL be present if verificationStatus is not entered-in-error. verificationStatus='entered-in-error' or clinicalStatus.exists()
ait-2 Rule AllergyIntolerance.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus!='entered-in-error' or clinicalStatus.empty()

Eric Haas (Jul 22 2019 at 18:05):

in this example the validator raises an error:... https://healthedata1.github.io/USCoreR4Validator/AllergyIntolerance-6267833.json.html

Eric Haas (Jul 22 2019 at 18:06):

where the verification status is 'entered in error' and clnical status is empty.

Eric Haas (Jul 22 2019 at 18:07):

I think in the expression verificationStatus='entered-in-error'... should be verificationStatus.code='entered-in-erro'r...

Eric Haas (Jul 22 2019 at 18:16):

also when this error appears...

[Unsupported system https://fhir.blah.blah.blah system is not specified or implicit]

Eric Haas (Jul 22 2019 at 18:17):

Does that only mean that GG's terminology server doesn't recognize the system?

Chris Moesel (Jul 22 2019 at 20:27):

I think in the expression verificationStatus='entered-in-error'... should be verificationStatus.code='entered-in-erro'r...

Actually, I think you need something more like this:

verificationStatus.coding.exists(code = 'entered-in-error') or clinicalStatus.exists()

It also accounts for the (likely rare?) case of verificationStatus having multiple codings defined.

Eric Haas (Jul 23 2019 at 00:11):

GF#22985, and GF#22986 (for Condition) @Michelle (Moseman) Miller These are R4 Technical Corrections and should be voted and FHIR-I and GG alerted.

Michelle (Moseman) Miller (Jul 23 2019 at 14:10):

I've added to Patient Care's agenda on Thursday

Grahame Grieve (Jul 24 2019 at 11:48):

how would I know, from these tasks, that they are R4 tasks? @Eric Haas I would not find them. @Lloyd McKenzie how should committees flag them?

Lloyd McKenzie (Jul 24 2019 at 11:53):

Target release of r4 (or stu3? Weren't sure if we're patching that too)

Grahame Grieve (Jul 26 2019 at 11:02):

we'll be a doing an R3 patch too, though only fixing broken invariants, I think

Deepak Poply (Nov 07 2019 at 15:01):

Hi All,

I'm trying to validate a Patient resource downloaded from FHIR site and getting below mentioned error

FHIR Validator Build ??
Arguments: C:\Users\dpoply\patient-example.json
.. connect to tx server @ http://tx.fhir.org
.. definitions from hl7.fhir.core#4.0.1
Installing hl7.fhir.core#4.0.1 to the package cache
Fetching:|
Analysing done.
(v4.0.1-null)
.. validate [C:\Users\dpoply\patient-example.json]
FAILURE validating C:\Users\dpoply\patient-example.json: error:1 warn:0 info:0
Fatal @ Patient (line 1, col2) : This does not appear to be a FHIR resource (unknown name 'Patient')

Please help.

Regards,
Poply

Lloyd McKenzie (Nov 07 2019 at 15:43):

Can you attach the instance from your machine?

Grahame Grieve (Nov 07 2019 at 20:05):

that's an old validator

Grahame Grieve (Nov 07 2019 at 20:05):

update to the latest

Lloyd McKenzie (Nov 07 2019 at 21:29):

@Grahame Grieve Do we know why the R4 FHIR spec continues to point to the old validator?

Grahame Grieve (Nov 07 2019 at 21:32):

it should not. If it does, it's because I haven't found the reference

Lloyd McKenzie (Nov 07 2019 at 21:37):

Downloads page validator link

Grahame Grieve (Nov 07 2019 at 21:38):

where exactly?

Lloyd McKenzie (Nov 07 2019 at 21:39):

The one that says "official fhir validtor" points to something on hl7.org/fhir rather than the build.fhir.org version

Grahame Grieve (Nov 07 2019 at 21:40):

hmm that reverted during the technical correction

Reece Adamson (Jan 07 2020 at 16:45):

Wasn't sure if I should create a new topic for this, but I'm seeing what I think is an issue with the validator.

Running: java -jar org.hl7.fhir.validator.jar allergy.json -ig hl7.fhir.us.core -version 4.0

Against this example resource: allergy.json

I get

java -jar org.hl7.fhir.validator.jar allergy.json -ig hl7.fhir.us.core -version 4.0
FHIR Validation tool Version 4.1.41-SNAPSHOT (Git# bdab9a78b39a). Built 2019-12-31T14:32:35.701+11:00 (7 days old)
Detected Java version: 1.8.0_222 from /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre on x86_64 (64bit). 3641MB available
Arguments: allergy.json -ig hl7.fhir.us.core -version 4.0
Directories: Current = /Users/radamson/Desktop, Package Cache = /Users/radamson/.fhir/packages
  .. FHIR Version 4.0, definitions from hl7.fhir.r4.core#4.0.1
  .. connect to tx server @ http://tx.fhir.org
    (v4.0.1)
+  .. load IG from hl7.fhir.us.core
   ... Using version 3.1.0
  .. validate [allergy.json]
Terminology server: Check for supported code systems for http://fhir.whatever.com/codes/AllergyClinicalStatus
*FAILURE* validating allergy.json:  error:1 warn:0 info:0
  Error @ AllergyIntolerance.clinicalStatus (line 8, col16) : None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/allergyintolerance-clinical|4.0.1 (http://hl7.org/fhir/ValueSet/allergyintolerance-clinical, and a code from this value set is required) (codes = http://fhir.whatever.com/codes/AllergyClinicalStatus#active, http://terminology.hl7.org/CodeSystem/allergyintolerance-clinical#active)

If I remove one of Codings from the clinicalStatus CodeableConcept, leaving only one Coding it passes. This is the second resource for convenience allergy2.json.

I would expect allergy.json to pass even with the extra Codings in the CodeableConcept as the required binding only requires that one of the Coding values SHALL be from the specified value set.

Am I doing or thinking about something wrong here? Happy to provide more information or test further.

Lloyd McKenzie (Jan 07 2020 at 16:47):

Yes, that seems like an error in the validator. Can you submit a change request?

Reece Adamson (Jan 07 2020 at 20:16):

FHIR-25424 created to track this

Grahame Grieve (Jan 10 2020 at 05:08):

ok thanks. fixed next release

Last updated: Apr 12 2022 at 19:14 UTC