01 - Various FML functions that are valid but the validator does not currently check them
Transform cast not checked yet (47 uses)
Transform evaluate not checked yet (2 uses)
02 - It is intended not to assign a variable
The source statement doesn't assign a variable to the source - check that this is what is intended (19 uses)
03 - This has been verified to be the actual FHIRPath expression needed to make the transform work. The error is incorrect - see https://chat.fhir.org/#narrow/channel/379173-FHIR-Mapping-Language/topic/.E2.9C.94.20evaluate.20transform.3F
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 'edt' is not valid for any of the possible types: [http://hl7.org/fhir/uv/omop/StructureDefinition/Measurement] (@char 1) (0 uses)
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 'eps' is not valid for any of the possible types: [http://hl7.org/fhir/uv/omop/StructureDefinition/Measurement] (@char 1) (0 uses)
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 's' is not valid for any of the possible types: [http://hl7.org/fhir/uv/omop/StructureDefinition/Measurement] (@char 1) (0 uses)
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 'src' is not valid for any of the possible types: [http://hl7.org/fhir/StructureDefinition/Observation] (@char 1) (0 uses)
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 'src' is not valid for any of the possible types: [http://hl7.org/fhir/StructureDefinition/Person] (@char 1) (0 uses)
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 'src' is not valid for any of the possible types: [http://hl7.org/fhir/uv/omop/StructureDefinition/DrugExposure] (@char 1) (0 uses)
The FHIRPath expression passed as the evaluate parameter is invalid: Error evaluating FHIRPath expression: The name 'src' is not valid for any of the possible types: [http://hl7.org/fhir/uv/omop/StructureDefinition/VisitOccurrence] (@char 1) (0 uses)
04 - Deprecated value set that is used in FHIR core
Reference to deprecated ValueSet http://hl7.org/fhir/ValueSet/jurisdiction|5.0.0 (61 uses)
05 - Codesystem is experimental but is used in Implementation Guide resource
Reference to experimental CodeSystem http://hl7.org/fhir/guide-parameter-code|5.0.0 (16 uses)
06 - This warning is all on Logical Models and we are matching the names of the elements in the OMOP tables.
Constraint failed: eld-20: 'The first component of the path should be UpperCamelCase. Additional components (following a '.') should be lowerCamelCase. If this syntax is not adhered to, code generation tools may be broken. Logical models may be less concerned about this implication. (path.matches('^[A-Za-z][A-Za-z0-9]{0,63}(\\.[a-z][A-Za-z0-9]{0,63}(\\[x])?)*$'))' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (654 uses)
08 - We are providing example concept maps and the FHIR resources do not have required bindings and neither do the OMOP bindings
The source variable does not have a required binding, so this concept map can't be checked (11 uses)
The target variable does not have a required binding, so this concept map can't be checked (14 uses)
09 - We are mapping to OHDSI terminology and this is a known limitation
The Target Code System https://fhir-terminology.ohdsi.org is not fully defined and populated, and no targetScope is specified, so the target code checking will not be performed (15 uses)
10 - These are example code systems we are using in our ConceptMaps and this is a known limitation
The Source Code System http://hl7.org/fhir/sid/cvx is not fully defined and populated, and no sourceScope is specified, so the source code checking will not be performed (1 uses)
The Source Code System http://loinc.org is not fully defined and populated, and no sourceScope is specified, so the source code checking will not be performed (2 uses)
The Source Code System http://snomed.info/sct is not fully defined and populated, and no sourceScope is specified, so the source code checking will not be performed (2 uses)
The Source Code System http://www.nlm.nih.gov/research/umls/rxnorm is not fully defined and populated, and no sourceScope is specified, so the source code checking will not be performed (1 uses)
11 - Explanation of conformance language in the conformance page
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The conformance verbs SHALL, SHOULD, and MAY are interpreted per RFC 8174.' (1 uses)
12 - Conformance language that is used in JIRA issue descriptions on the change log page
No conformance term found in the text: (2 uses)
No conformance term found in the text: 3.3, along with a forward reference to the full explanation in (2 uses)
13 - We have a code system that defines our requirements categories. These are FHIR to OMOP-specific so they won't be moving to THO. We also define an abstract code so we can easily create the value set. (See https://confluence.hl7.org/spaces/TSMG/pages/482410656/2026-07-30+TSMG+Agenda+and+Minutes for TSMG waiver)
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
The property 'abstract' has no definition in CodeSystem.property. Many terminology tools won't know what to do with it (1 uses)
14 - We want to associate our requirement categories to the Requirements-Category code system but it is not in THO yet. When it does, we will fix the property to use that code system. For now, we are specifying the codes without a code system.
A code with no system has no defined meaning, and it cannot be validated. A system should be provided (12 uses)
hl7.fhir.uv.omop
hl7.terminology.r5
