I m ok but please not face show normal goggle Love Gill, Organization 1 year ago
Good Alice SMB, none 8 months ago
Obsolete Multiaxial Parts in PartChangeSnapshotAll of the changes to the Multiaxial hierarchy (MAH) for the June 2019 release resulted in the creation of thousands of new Multiaxial Parts as well as to thousands of existing Multiaxial Parts becoming obsolete. Because most Multiaxial Parts are not directly linked to LOINC terms, they are not published in the Part file, so all of the obsolete Parts would have disappeared with no record of ever having existed, except in prior versions of the MAH file. To avoid confusion, we included all of these Parts in the Change Snapshot file so that there is documentation of their existence and deprecation.
Inactive Parts in PartChangeSnapshotWith each release, a small number of Parts that were linked to a LOINC term in the previous release become unlinked. Because only Parts that are linked to a published LOINC are included in the Part file, such unlinked Parts that were present in the last Part file would disappear. To address this, we decided to change the status of such Parts that became unlinked to Inactive and include them in the PartChangeSnapshot file. Is it useful to know which Parts became Inactive since the last release?
Types of changes in LoincChangeSnapshotThe inaugural release of the LoincChangeSnapshot file includes all terms that had a change in Status since the last release, such as from TRIAL to ACTIVE, or ACTIVE to DEPRECATED. Which other types of term changes would it be useful to include in this file?
LOINC Changes File and Report versus LoincChangeSnapshotWe are considering transitioning away from publishing the LOINC Changes File and LOINC Changes Report in lieu of the LoincChangeSnapshot file. The original Change File and Report include two rows ("BEFORE" and "AFTER") per term, where the actual change can be found by comparing the two rows. The LoincChangeSnapshot file has a row per change, where the fields include the effective version of the change, the attribute whose value changed, the prior value, the current value, and the change reason. (Note that the initial LoincChangeSnapshot release only contains terms that had a change in status since the last release.) If multiple changes occurred for one term, each of those changes would be documented in a separate row. Which format is more useful?
Snapshot versus Running historyAs currently designed, the ChangeSnapshot file would only include changes to Parts and terms since the last release, meaning that the contents of the file will be completely different from release to release. If we were to publish a running history instead, then with each release, the change rows would be appended to the previous publication, and over time every change to a given term would be included in a single file. We are inclined to publish the snapshot, but would consider a running history instead if the majority of users would prefer that format. Of note is that it may be difficult (i.e. time consuming) to fully recreate the past history from all prior LOINC releases.