Releases: nightingaleproject/VRDR_javalib
Releases · nightingaleproject/VRDR_javalib
v1.4.1-STU2.1
v1.4.1-STU2.1 - 2023-04-20
- Numerous bug fixes found as part of testing certification with UT
- Race Literal handling update as per VRDR IG
v1.4.0-STU2
- Added support for VRDR Messaging IG
- New package "messaging" for VRDR Messaging IG models
- New package "messaging.util" for messaging helper classes separate from the IG models
- VRDRFhirContext now contains all data structure and messaging definitions and is the primary context use case
- New class VRDRFhirContextDataStructuresOnly is a context class with only the data structure definitions
- New package edu.gatech.chai.VRDR.messaging contains all messaging structure definitions in the IG
- Besides IG classes, messaging also contains BaseMessage and UnknownMessage classes for assisting in message handling
- New class MessagingTest contains thorough messaging tests for VRDR Messaging IG flows
- Test resources now contains FHIR json and xml files for use by the MessagingTest class
- Generic parser method on BaseMessage for parsing bundles and messages
- Added xml and json test files and tests
- Added CauseOfDeath and Demographics coded bundle handling
- Tests complete for all major flows
- Added CLI for generating canary tests
- Added CHANGELOG for tracking changes with each release
- Updated README
v.1.3.5-STU2
v.1.3.5-STU2
- Moving from ig1.3 branch to master branch as mainline. Master branch will be the most current version of VRDR moving forward
- Changed naming scheme from v{version}-STU1.3 -> v{version}-STU1.3 to appropriately reflect the version of guide that the library suspports.
- Removed old resources not supported in STU2
- Fixed a major issue with resources not being added to the correct section of the DeathCertificate
- Fixed many valuesets that were missing values
- Fixed partialdatetime on surgerydate
- Added missing birthrecordidentifier birth year setting
- Added constraint to DecedentAge to constrain values to either years(a) or months(mo)
v1.3.4-STU1.3
- Fixed a recursive function bug in CauseOfDeathPart1
- Fixed a custom resource addition on the DeathCertificateDocument
1.3.3-STU1.3
- Reverting from NVSS Race and Ethnicity Set back to us-core race and ethnicity definitions
- Cleaned up the jurisidictional ID valueset, moving towards AddressUtil, and made it more clear in the BuildDCD definition how to work with the jurisdictional-ID extension valueset.
- 2nd try at release
1.3.2-STU1.3
- Updated incorrectly named resources
- Enabled Death Certicate sections
- Enabled ease of access for jurisdictional ids to be easier to set on addresses
- Added missing EmergingIssues resource
v1.3-STU1.3
Major Breaking changes.
If you are moving from STU1.2 to STU1.3 you will experience breaking changes.
- Changing packaging name from --<ig_version> to simpler: -<ig_version>. VRDR_IG will not be updating FHIR versions, and if they are, a fhirversion will be included in a base package version, but no subsequent versions
- Updated resources to conform to STU1.3
- Created common jurisdiction-id extension handler
- Moved CauseOfDeathCondition and CauseOfDeathContributingCondition to Observation base
- Added interval handler to CauseOfDeathCondition
- Added auxillaryStateIdentifer extension to DeathCertificateDocument
- Updated Decedent Race and Ethnicity extension to use specific boolean and yesnounknown valueset type definitions
- Using a "Literal" subextension type under Race or Ethnicity will capture the value as a string, allowing the user to specify any Race/Ethnicity they choose
- Added a common AddressUtil to support extensions applied across all Address types in VRDR
v1.3.1-STU1.3
Major Breaking changes.
Added CodedCauseOfDeathBundleContents
Added Common Messaging Support
v1.2.3-R4-STU1.2
- Added missing juridiction ids
- Added death location type valueset with common string constructor
- Remove all OIDs from value definitions. All value definitions will be describe in source system urls now, not by valueset oids. Even where VRDR_IG specifies otherwise (currently)
v1.2.2-R4-STU1.2
- Fixed jurisdiction Id extension not adding to record when testing.
- Added 2 letter FIPS codes as searchable codes for jurisdictional ids even though not supported in valueset. Can add jurisdictional Id as : "13","GA" or "Georgia" for example
- Fixed missing "urn:oid" prefixes on all systems.
- Fixed an issue related to the detailed component on decedent race being mistakenly set as the ombcategory