Skip to content

Conversation

@grongierisc
Copy link

Fell free to review this PR, it's brings an initial support of HL7v2 to FHIR.

Tested on ADT, ORU.

Details of modifications and issues in the Readme.

Feedback are welcome.

TODO :

  • Build unittest
  • Test all examples

…me, STCoding, XCNPractitionerRole, DR, DRPeriod, SNQuantity, XONString, CWEstring, SAD, CWEDuration, EDAttachment2, ISCodeableConcept, TQTask, CWETiming_Duration, MOMoney, Author, Source, PatientCongregation, ClaimResponse, Basic, Flag, Goal, List, Media, NMQuantity, Condition-dueTo, Owner, Subject, Account, Enterer, Insurer, Patient
- Refactor generate_id_input filter to include the base ID in the generated input string if required.
- Refactor sign filter to cast the given data string as an integer or float and return -1 if negative, 1 if positive, and 0 if zero.
… decoding errors, and improve segment rendering logic
…ect UTC offset handling; update tests for expected output format
…ation; update encode_io function and related imports
…place with json-five for improved efficiency
…TQ_SupplyRequest; correct XTN condition check
- Updated version in pyproject.toml to 0.5.0 and adjusted python-liquid dependency to ^2.0.0.
- Refactored test_filters.py to replace deprecated exceptions and methods from Liquid 2.0.
- Added new test_liquid_extensions.py to validate FHIR compatible path syntax.
- Updated test_loaders.py to accommodate changes in Liquid 2.0, including loader adjustments and removed cache assertions.
- Modified test_renderers.py to reflect changes in Liquid 2.0 regarding auto_reload and cache properties.
- Temporarily disabled custom tag tests in test_tags.py and added basic tests for environment functionality.
- Created test_tags_old.py to retain original tests for future reference during migration.
- Introduced a comprehensive technical guide covering:
  - Quick start instructions for basic usage and custom templates
  - Detailed explanation of HL7v2 message structure and parsing process
  - In-depth exploration of Liquid template usage and custom filters
  - JSON5 processing details, including merging behavior and automatic removal of empty fields
  - Advanced topics on custom template creation and error handling
  - Troubleshooting section addressing common issues and debug techniques
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant