Releases: luisfabib/fhircraft
v0.7.1
Added
- Added
skip_invalidparameter toStructureDefinitionRegistry.download_packageandFHIRModelFactory.register_packageto gracefully skipStructureDefinitionresources that fail validation, issuing a warning instead of raising an error (#327) - Added
include_dependenciesparameter toStructureDefinitionRegistry.download_packageandFHIRModelFactory.register_packageto control whether package dependencies are automatically downloaded and registered alongside the requested package (#327)
Fixed
- Fixed
toDate()/convertsToDate(),toDateTime()/convertsToDateTime(), andtoTime()/convertsToTime()to supportdate,datetime,time,System.Date,System.DateTime, andSystem.Timetypes rather than returning empty lists (#320, fixes #328) - Updated the regular expression in
toDecimalandconvertsToDecimalto correctly recognize numbers with a leading plus sign, enabling support for strings like "+14" and "+14.5" in conversion functions (#321, fixes #309) - Ensured that the FHIRPath
now()function always returns a time-zone awareDateTime(fixed to the UTC offset) as required by the FHIRPath specification (#322, fixes #312) - Fixed the propagation of any UTC offset from timezone-aware Python
datetime/timeobjects into the FHIRPathDateTime.hour_shift/DateTime.minute_shiftfields, preserving timezone information through serialization and comparison (#322) - Fixed the FHIRPath
DateTime/Timeliterals string parsing to ensure theZsuffix (UTC shorthand) is parsedashour_shift = 0/minute_shift = 0(#322)
- Fixed spelling errors in the FHIRPath lexer calendar duration tokens list by replacing "miliseond" and "miliseconds" with the correct "millisecond" and "milliseconds" (#323, fixes #313)
- Introduced
TypePrecisionErrorto signal that a comparison cannot be performed between FHIRPath values with different levels of precision, allowing equality operators to propagate an empty collection per the FHIRPath spec (#324) - Refactored FHIRPath
TimeandDateTimeliterals to store seconds asfloat(combining seconds and milliseconds) instead of separatesecondandmillisecondinteger fields, improving sub-second precision handling (#324) - Fixed
to_time()andto_datetime()conversion methods to propagate timezone offset (hour_shift/minute_shift) into the returned Pythontime/datetimeobjects. (#324) - Fixed
TimeandDateTimeliterals string parsers to accept 1–3 digit millisecond values and correctly combine them with the seconds field as a float (#324) - Fixed
NotEquals(!=) operator to return an empty collection when the operands are empty or of incompatible types, instead of incorrectly inverting a non-boolean result (#324, fixes #305) - Fixed
Equivalent(~) string comparison to normalize internal whitespace (collapsing runs of whitespace to a single space) in addition to trimming and lowercasing. (#324, fixes #311) - Fixed
Equals(=) andEquivalent(~) to return an empty collection when aTypePrecisionErroris raised during comparison of values with differing precision levels (#324) - Refactored
All.evaluate()to use.single()for criteria evaluation so
that single-item results are correctly unwrapped (#324) - Update
validate_FHIR_element_pattern()to useis_dict_subset(_pattern, _element)instead ofmerge_dicts(_element, _pattern) == _elementto ensure that pattern containment is properly executed (#325, fixes #317) - Ensured that extension placeholder fields for primitive type-choice variants (e.g.
value[x]) are now named after the concrete typed field (valueString_ext,valueBoolean_ext, …) rather than the polymorphic base name (value_ext) (#330, fixes #329) - Fixed factory to preserve base-type cardinality through differential merging such that profiled models no longer silently change array-fields into singleton ones (#337, fixes #331)
- Prevented
SlicedFieldBuilderfrom emitting a redundant serialization alias when the field name was not renamed (#337, fixes #332) - Fixed backbone field builder to short-circuit
build()and return the original specific backbone type directly when the differential has no children, instead of generating an empty subclass (#337, fixes #333) - Fixed
SnapshotResolverto correctly resolve all base elements when an intermediate profile in thebaseDefinitionchain has no snapshot (#337, fixes #334) - Ensured that extensions on complex type fields are correctly accounted for and generated by the model factory (#337, fixes #335)
- Implemented handling of prohibited fields (
0..0) to be set asNone-typed fields in the builder (#337) - Updated
ElementNode.documentationretrieval to skip non-alphanumeric-only content in theshort,definitionandcomment(#337) - Fixed
max_cardinalitytype annotation to allowNonein generated source code (#337) - Ensured that multiple type codes on an element definition are supported in the factory resolver (#337)
v0.7.0
Added
-
Implemented a new modular factory architecture (#296)
- Added a new
factorypackage with dedicated sub-modules:element_node,index,resolver,context,assembler,core, andexceptionsreplacing the previous monolithicfactory.py. - Added Specialised field builders
BaseFieldBuilder,SimpleFieldBuilder,BackboneFieldBuilder,SlicedFieldBuilder, andTypeChoiceFieldBuilder, each responsible for compiling field information for a specific class of FHIR element. - Implemented a new
StructureDefinitionRegistrydedicated registry for loading, storing, and resolving FHIRStructureDefinitionresources, including dependency resolution via FHIR packages. - Cleaned and streamlined the public API for
FHIRModelFactoryfor long-term stability- Renamed
construct_resource_modeltobuild - Renamed
load_packagetoregister_package - Renamed
add_structure_definitiontoregister - Renamed
clear_cachetoreset_cache - Added new methods
get_registered_definition,has_registered_definition,unregister,list_registered_definitions,rebuild,is_built,list_built,evict
- Renamed
- Added a new
-
Implemented a
FHIRTypeRegistrycentralised registry for resolving FHIR type names and canonical URLs across all FHIR releases (R4, R4B, R5) (#296) -
Added support for to correctly handle slicing rules, particularly
closedslicing (#296) -
Introduced FHIRPath expression parse caching so that identical expressions (common for FHIR invariant constraints) are compiled by PLY only once per process lifetime rather than on every constraint evaluation significantly reducing computation times (#299)
Added aStructureMapRegistrythat operates offline by default. StructureMaps must be registered before execution; the engine raises a clear error if an imported URL is not found. An optional internet fallback can be enabled to resolve canonical URLs at runtime (#300) -
Added support for the
importclause: the engine now resolves canonical URLs declared in a StructureMap'simportsection, making groups defined in those maps available during execution. Wildcard URLs (e.g.http://example.org/maps/*) are supported and matched against all registered maps (#300, fixes #37) -
Added support for the
extendsclause, including: multi-level inheritance chains and cross-map inheritance (#300, fixes #33) -
Added a specific FHIR Mapping Language parser error message for the common scenario when a rule was not closed with a semicolon, providing a clear hint (#302)
-
Added support the FHIRPath
Systemtype namespace (#303)
Changed
- Consolidated the FHIR type utilities; all type lookups now go through a single
get_fhir_typefunction backed byFHIRTypeRegistry(#296) - Set the
ElementDefinition.idfield set as aStringprimitive rather than anIdprimitive to avoid the inconsistency between theIdprimitive regex constraints and the functional meaning for theElementDefinition(namely the use of colon:) (#296) - The resource factory no longer injects
meta.profilewith default values into constructed models (#296) -
- Renamed several of the configuration parameters for clarity and precision (#298)
- Renamed
disable_warningstodisable_validation_warnings - Renamed
disable_warning_severitytodisable_fhir_warnings - Renamed
disable_errorstodisable_fhir_errors - Renamed
disabled_constraintstodisabled_fhir_constraints
- Renamed
- Renamed several of the configuration parameters for clarity and precision (#298)
- Renamed
with_config()context manager tooverride_config()for clarity and consistency (#298) - Froze
FhircraftConfigto raise an error upon direct attribute mutation (#298) - Extended all constraint, pattern, fixed-value, type-choice, and cardinality validators to respect configuration
mode = 'skip'by returning immediately (#299) - Extended all assert-based validators (pattern, fixed-value, type-choice, cardinality) to respect configuration
mode = 'lenient'by issuing warnings instead of raising errors, consistent with how FHIRPath constraint validators already behaved (#299) - Switched resource context computation in FHIR models and lists to be lazy, deferring work until the context is actually accessed rather than computing it at construction time (#299)
- Renamed the
repositoryattribute onFHIRMappingEnginetostructure_definition_registryto better reflect its purpose and distinguish it from the newstructure_map_registry(#300) - Introduced
FHIRStructureMapperas the new public interface for the FHIR Mapping Language. The oldFHIRMapperis replaced byFHIRStructureMapper(#318)
Fixed
- Enhanced the factory builder type resolver to detect elements with primitive FHIRPath-types and, consequently, to not generate extension placeholder elements (
*_ext) and to use thestructuredefiniton-fhir-typeto determine the proper FHIR-native primitive type to use. (#296, fixes #290) - Removed primitive extension placeholder elements from built-in model fields with FHIRPath types (
Element.id_ext,Extension.url_ext,Xhtml.value_ext, and all downstream models) and updated their type ofExtension.url(StringtoUri) and ofElement.id(StringtoId) across all releases (R4, R4B , R5) (#296, fixes #288) - Ensured that sliced field type unions and their referenced slice models use concrete base element types (e.g.
ObservationComponent) rather than base types (e.g.BackboneElement) when constructing sliced elements in differential mode (#296, fixes #292 and #293) - Fixed sliced field construction to correctly inherit slices already defined on the parent model's field when constructing sliced in differential mode (#296, fixes #294)
- Fixed multiple issues related to differential resolution including (#296)
- Ensured that intermediate-node path lookups not defined in the differential are accounted.
- Fixed the resolution so that a differential is always resolved agains a snapshot and not against a partially resolved differential.
- Enabled support for recursive resolution against a sequence of base definitions.
- Fixed
Dosage.doseAndRate(R4, R4B, R5) polymorphic fields (doseQuantity,rateQuantity) to now correctly referenceQuantityinstead ofSimpleQuantityin the validator and correctly validate values (#296) - Fixed the
validate_slicing_cardinalitiesvalidator to correctly handleNonevalues in themaxcardinality (#296) - Updated the slice cardinality validator to only validate cardinalities when at least one slice instance is present, consistent with how element cardinalities are handled and avoiding false violations when a discriminator cannot be evaluated (e.g. value-set binding slices) (#296, fixes #295)
- Replaced
**kwargsinconfigure()andoverride_config()with explicit keyword-only typed parameters; unrecognized arguments now raiseTypeErrorat call time (#298, fixes #208) - Fixed parser to allow declarations in any order within FHIR Mapping Language scripts, rather than requiring a strict fixed sequence. (#302, fixes #301).
- Updated the parser to raise
FhirMappingLanguageParserErrorwhen themapstatement appears more than once in a single script (#302)
Removed
- Replaced the monolithic
factory.py(2,200+ lines) by the newfactory/package (#296) - Replaced the
StructureDefinitionRepositorymodule and its associated tests, now superseded byStructureDefinitionRegistry(#296) - Removed
ValidationConfigdataclass and merged its fields directly intoFhircraftConfig(#298)
v.0.6.5
Added
- Added an "AI Tools and Human Attribution" info box to the contributing guidelines, outlining acceptable and unacceptable types of AI-assisted contributions, and emphasizing the requirement for human review and responsibility (286)
- Implemented a manifest-based FHIR resource
StructureDefinitionlookup system for factory model construction based on canonical URL and name for performance and stability (281)
Changed
- Splited the
definitions/R{x}/profiles-resources.jsonanddefinitions/R{x}/profiles-types.jsonfiles into individual files containing just the bundledStructureDefinitionresources, largely decreasing the overall package size (281)
Fixed
- Added support for the logic that allows correctly creating models for slices of primitive types with extension placeholders, improving compatibility with FHIR extension patterns (#276)
- Fixed errors in factory methods when trying to load structure definitions of complex-type resources (#281)
- Fixed the differential element merging to recursively merge parent elements in the element path hierarchy. This ensures all intervening elements are created and properly merged with base definitions (#278, fixes #279)
- Fixed an issue with the differential merging to ensure that it succeeds even if the base definition has a different base name as the derived resource (#278)
- Ensured that when constructing differential mode profiles, specialized BackboneElement subclasses from the base model are used as bases instead of generic BackboneElement, allowing proper inheritance of backbone element structure (#283, fixes #277)
- Prevented identical inherited properties from being in generated source code of derived classes, while still generating properties that are new or have different implementations (#285)
v0.6.4
Fixed
- Ensured that profiled complex types with pattern or fixed values result in the correct default type when set (#269, fixes #111)
- Sanitized StructureDefinition.name values to ensure valid Python class identifiers (#269, fixes #264)
- Fixed cardinality resolution to fall back to base model when not resolved in structure definition (#269)
- Fixed the construction of slice models by passing the correct base class for constructing its element fields (#269)
- Changed the representation of fixed-value constraints from
EnumandLiteralto proper Pydantic field validators to ensure correct functionality even for complex values (#269, fixes #263) - Enabled polymorphic deserialization for profile models to accept instances of their parent classes, matching the behavior of dictionary deserialization. Profile fields now properly validate and adopt parent class instances while preserving all data (#270, fixes #262)
- Ensured FHIR Pydantic fields are always nullable independently of default value (#269)
- Updated the model source code generation logic and template (#272, #271)
- Removed hardcoded import statements in favor of dynamically generated imports, ensuring that only the required modules and objects are imported for each generated resource (#272, fixes #261)
- Removed the
model_rebuild()calls to avoid unnecessary model rebuilds (#271, fixes #261) - Avoided setting field descriptions when explicitly set as
Noneor empty strings (#269)
- Prevented the resource factory of creating empty slice models if there are no fields and no validators specified for the slice (#273, fixes #265)
v0.6.3
Fixed
- Improve code generator to reduce boilerplate and repetitive code in auto-generated model definitions source code (#256)
- Updated the code generator to serialize and include non-built-in bases in generated code, enabling proper handling of custom base classes
- Fixed the factory method for differential elements resolution to ensure properties such as constraints are not reintroduced if not specified by the differential definition
- Fixed the code generator to also check in ancestor bases of the requested models for inherited validators
- Prevented unnecessary class variable definitions from being inherited from parent classes to avoid duplicate
- Resolve bug in factory when dealing with differentials that slice an element within a complex or backbone type. When profiling
Observation.code.coding:slice, the slice cannot be resolved against the base becauseObservation.code.codingis implicitly derived fromObservation.code's type rather than explicitly defined in the snapshot. This causes the sliced element to lose type information and be omitted from code generation (#257, fixes #255) - Ensured that when merging the differential element definitions, if the sliced element's ID is present in the base snapshot, then it is resolved against it with fallback to resolution against the path (#257)
- Pattern and fixed-value constraints on slices are now enforced. When a slice definition includes pattern values such as
patternCodeableConcept, the generated model will validate slice instances against the specified pattern and include appropriate default values. (#259, fixes #258) - Limited polymorphic deserialization to abstract FHIR resource classes (
_abstract=True) to avoid pollution of deserialization of other classes after creating new resource models (#258)
v0.6.2
Added
- Added support to the FHIRPath
resolve()function for resolution of internal references when the%resourceenvironment variable is available (#252) - Added support for implicit FHIRPath evaluation context to the
evaluatetransform during mapping (#246, fixes #39 and #217) - Added support for implicit type casting to the
casttransform during mapping (#246, fixes #38) - Added support for implicit system detection to the
cptransform during mapping (#246, fixes #40)
Changed
- Updated the FHIR Mapping Language parser to no longer strip quotes from FHIRPath expressions, ensuring that string FHIRPaths within the mappings (e.g. constants) retain their quotes during parsing (#251, fixes #213 and #216)
- Removed support to the FHIRPath
resolve()function for attempting resolution of URL references using the reference as absolute URL for security reasons, now warning instead (#252)
Fixed
- Fixed resolution of FHIRPaths within source context scopes for the
whereandcheckstatements (#246, fixes #215) - Fixed documentation mapping examples not returning the correct results (#246, fixes #220)
- Fixed transforms to allow variables to be passed as arguments (#246, fixes #218)
- Expanded the FHIR Mapper parser grammar to allow reserved words (e.g.
group,import,source, etc.) to be used as identifiers both in mapping rules and its FHIRPath expressions (#250, fixes #214) - Modified the FHIRPath
Literalclass so that the string represenations of date, datetime, and time values are represented with an@prefix (e.g.,@2014-01-01), aligning with FHIRPath conventions (#249, fixes #247) - Fixed the string representation of FHIRPath index invocations (e.g.,
a[2]), which was previously represented with a dot (#249, fixes #248) - Ensured that
resource_urlcannot be evaluated toNonewithin the FHIRPathresolve()function, which was leading toAttributeError(#252, fixes #240) - Fixed XML serialization to wrap contained/nested resources in their respective resource type tags during XML serialization (#253, fixes #219)
v0.6.1
Added
- Implemented one official FHIR example file for each core FHIR resource and a corresponding unit test to validate core resource model compliance across R4, R4B, and R5 releases (#244)
Changed
- Removed redundant validator methods and duplicate field definitions that unnecessarily overrode their inherited counterparts from the base class (#236)
Fixed
- Added missing aliases for fields containing reserved keywords (e.g.
class_,import_, etc.) in 15+ resources across R4, R4B, R5 ensuring correct (de)serialization (#227) and ensured they are properly evaluated in FHIRPath (#233) - Added missing
_typemetadata attribute to the R4CommunicationRequestclass (#229) - Added validation to ensure the FHIRPath
iif()function only operates on singleton collections, fixed criterion evaluation for empty input collections instead of iterating over collection items, and added type checking to ensure criterion evaluates to a boolean value (#231, fixes #230) - Fixed FHIRPath comparison operators when comparing
Quantitysubclasses such asAge,Duration, etc. (#232, fixes #226) - Updated the
ref-1constraint validation logic to skip evaluation when_root_resourceor_resourceattributes are not set, preventing FHIRPath evaluation errors (#234) - Changed the FHIRBaseModel context setup for complex types by ensuring
_resourceand_root_resourceare only set for actual FHIR resources and children objects, not root complex datatypes (#234) - Added the missing backbone elements for the elements of the R5
Availabilityclass (#236)
Ensured that theListexposed in thefhircraft.fhir.resourcres.datatypes.R5.coremodule is the FHIR model and nottyping.List(#236) - Improved the FHIRPath
comparable(),lowBoundary(),highBoundary(),toQuantity(), andtoString()functions to work withFHIR.Quantitytypes and subclasses (#238) - Fixed issue in FHIRPath
comparable()function to returnFalsewhen one of the input values evaluates toNone, conforming with the FHIRPath specification for this function (#239) - Fixed errors during validation due to
%resourcenot being defined by moving all FHIR invariant constraint validators in classes inheriting fromBackboneElementto their core resource parent class to ensure they evaluate within the context of the full resource (#236) - ixed FHIRPath math operators (addition, subtraction, multiplication, division) to work with mixed FHIRPath and FHIR
Quantitytypes and with quantities of different (compatible) units (#238) - Fixed
toString()conversion to properly extract unit fromFHIR.Quantityobjects (#238) - Fixed handling of UCUM unit codes with special characters (square brackets, quotes, curly braces) to ensure that UCUM unit codes such as, e.g.
mm[Hg],{fractions}, or[arb'Unit]are properly processed by FHIRPathQuantityobjects (#238) - Added missing
manufactured_item_definitionandnutrition_productimports to the R4B core module (#241) - Added missing
resourceTypefield to the R4BExampleScenarioInstanceclass (#241) - Updated the initialization of
UnitRegistryin FHIRPathQuantityliterals to setautoconvert_offset_to_baseunit=True, ensuring offset units are automatically converted to their base units (#243, fixes #242)
v0.6.0
Added
- Added support for differential-based FHIR model construction allowing more efficient resource creation and modification (#156)
- Established using the
StructureDefinition.differentialas default behavior for contructing FHIR resource models. - Introduced
construction_modeconfiguration to the resource factory withSNAPSHOT,DIFFERENTIAL, andAUTOmodes to control how to build resource models from structure definitions
- Established using the
- Added support for XML (de)serialization of FHIR resources through the new methods
model_dump_xmlandmodel_validate_xml(#154) - Added support for mapping arbitrary structures as sources in FHIR Mapping Language enabling more flexible data transformations without requiring a strict structure definition (#153)
- Added support for nested target elements in FHIR Mapping Language parser to detect nested target paths and recursively expand them into intermediate targets with generated variables and nested rules, following the FHIR specification (#160)
- Added suuport for identity transforms and default group mappings in the FHIR Mapping Language engine (#165, fixes #164)
- Enhanced the mapping engine to track groups with
StructureMap.group.typeModeoftypesortype-and-typesand makes them available for automatic invocation when using default mapping rules. - Introduced an internal
_DefaultMappingGroup_symbol both for the FML parser and mapping engine to denote a dynamic mapping group that resolves into an appropriate default mapping group based on type context, with fallback to a simple copy group.
- Enhanced the mapping engine to track groups with
- Overhauled the documentation (#184)
- Added new user guides with better storylines, clearer explanation, better examples and with references to external resources
- Restructured the technical API reference for better navigation and removed internal (private) API documentation
- Added a new suite of tests that ensure that all documentation examples are error-free.
- Added
ElementDefinitionmodels missing for all FHIR releases (R4, R4B, R5) (#189) - Missing nested backbone elements in
Dosage,TimingandDataRequirementscomplex types across R4, R4B and R5 (#224) - Added multi-release FHIR Support for mapping parser and engine (#221)
- Added new class variables to all
FHIRBaseModelsubclasses to contain FHIR metadata (#212)- Added
_abstractto indicate concrete resource implementations - Added
_typefield containing the FHIR resource type name to replace the now removed Pydantic fieldresourceType - Added
_canonical_urlcontaining the official HL7 FHIR structure definition URL
- Added
Changed
-
All Pydantic FHIR models now forbid extra fields for enhanced validation and strict FHIR conformance (#223)
-
Updated the FHIRPath and FHIR Mapping Language parsers and lexers to reduce overhead and wasteful instantiation greatly improving overall performance (#155)
-
Updated the type choice validator
validate_type_choice_elementto also check for the absence of types not permitted by the structure definition (#156) -
Updated the FHIRPath mixin methods now include optional
environmentargument for custom environment variables (#169, fixes #166) -
Changed FHIR model fields validation to support both name (
validate_by_name) and alias (validate_by_alias) validation (#175) -
Changed the FHIR Mapping Language comment handling to ignore comments rather than attempting to parse them as
StructureMapdocumentation elements (#182) -
FHIR constraint validators refactored from field-level to model-level validation for proper environment access (#201)
-
Added multiple checks to raise errors in the mapping engine if critical elements are not set in the
StructureMapresource (#188) -
Refactored all FHIR element constraint validators from Pydantic's
@field_validatordecorator to@model_validator(mode="after")to ensure FHIRPath invariant constraint evaluated on fully built instances with access to environment variables (#201, fixes #190) -
Updated the repository and factory methods to now use version-specific models instead of a bootstrapped
StructureDefinitionandElementDefinitionmodel. Avoids lost version-specific data when version-specific fields that were ignored during validation or during round-trip validation (#210)
Fixed
- Improved the behavior of the code generator for factory-generated models, nested annotations, and type alias serialization (#156, fixes #138)
- Updated the
GreaterThan,LessThan,LessEqualThanandGreaterEqualThanFHIRPath operators to treat zero (0) as a valid value, preventing it from being skipped in comparisons (#158, fixes #157) - Fixed the evaluation of the FHIRPath
Alloperator to properly evaluate the boolean values returned by the criteria expressions (#158) - Fixed
Extensionfield types to use forward references to avoid import errors on runtime (#159) - Fixed the FHIRPath equality operator string representation to use single equals sign (
=) to fix errors encountered during mapping (#163, fixes #161 and #162) - Updated the FHIRPath parser to support type specifiers containing resource names like
FHIR.Patient(#170, fixes #170) - Updated the FHIRPath engine to support arguments of type
FHIRPathin functions already takingLiteraltype values allowing runtime evaluation of dynamic input arguments (#172, fixes #171) - Fixed the FHIRPath lexer to correctly handle escaped quotes (
\'and\") in strings supporting escape sequences usch as regexes (#181, fixes #181) - Improved the code generator's handling of
default_factoryvalues containing lambda-functions orBaseModelinstances (#183, fixes #180) - Fixed multiple bugs in the FHIR Mapping Language engine (#188)
- Fixed a bug leading to resolvable structure types not being recognized and treating all targets as
ArbitraryModelinstances and returning dictionaries (Fixes #187) - Fixed structure definition resolution logic in mapping engine to use
StructureDefinition.nameas default alias when not specified - Fixed HTML validation issues in FHIR Mapping Language parser when setting
StructureMap.textwith HTML-escaping mapping content
- Fixed a bug leading to resolvable structure types not being recognized and treating all targets as
- Fixed a
TypeErrorin FHIRPathUnionoperation by removing unnecessary sorting that failed when collections contained incomparable types (#196, fixes #194) - Fixed the environment variable precedence issue where default FHIRPath variables (
%context,%resource,%rootResource,%fhirRelease) were overriding user-provided environment variables in nested evaluations. Custom environment variables now properly take precedence over system defaults when both are present (#197, fixes #193) - Resolved FHIRPath ambiguity issues where negative numbers conflicted with subtraction operators (#198, fixes #198)
- Replaced
type.code.contains(':')withtype.select(code.contains(':')).exists()for the official FHIReld-11constraint validation expression inElementDefinitionclass for R5 release to properly handle collections with multipletype.codevalues (#199, fixes #195) - Fixed the incorrect resolution of the $this variable in FHIRPath expressions when used within nested function calls. Previously, $this would maintain the outer collection item context instead of updating to reflect the current evaluation context for certain FHIRPath functions ([#203](https://github.co...
0.5.0
Added
-
Added a new configuration module that provides thread-safe global and context-local configuration management, and exposes functions for configuring, resetting, and modifying validation settings. This includes context manager support and environment variable loading (#150)
-
Added configuration parameters to control how validation of FHIR resource invariants is executed, including their severity, type of feedback, or completely skipping their validation. (#150)
Changed
- Changed the logging level from
infotodebugfor log entries created by the FHIRPathtracefunction. (#147)
Fixed
-
Added the
packagingmodule as a core dependency to avoid import errors ifpytestis not installed in the executing environment. (#149, fixes #148) -
Updated import statements in core FHIR resource modules to alias
typing.ListasListTypewhere necessary to avoid overshadowing the FHIRListmodel. (#151, fixes #139)
0.4.2
Changed
- Added thread-local stacks to track recursion during polymorphic serialization and deserialization, preventing infinite recursion in nested FHIR resource structures. This replaces the previous global flag approach for recursion protection. (#142)
Fixed
- Removed the
generic_FHIR_resource_validatormethods for the outcome, resource, and issues fields in the Bundle resource for R4, R4B, and R5. Since these were calling the previously removedvalidate_contained_resourcean error was raised whenever evaluating aBundle(#140) - Modified
FHIRBaseModel._serialize_fhir_field_polymorphicallyandFHIRBaseModel._deserialize_polymorphicallyto remove temporary disabling of polymorphic flags, relying instead on stack-based recursion protection. This ensures that nested resources are handled correctly and safely. (#142, fixes #141)