Production (January 2019 International Release OPTIONAL package (PUBLISHED)) vs UAT (July 2019 International Release OPTIONAL package) VERSION 5 traceability
Differences found in package Comparison | Number of records impacted | Rationale | |
|---|---|---|---|
| RefsetDescriptor files | 1 | 1 record updated with the new attributeType ("URL" instead of "parsable string), as expected in ISRS-583: < a87a81a3-b10c-490b-9cc1-d94fafc5dc27 20170731 1 900000000000012004 900000000000456007 723560006 723570008 707000009 7 Same as International published release | |
| Concept files | 10029 | 2463 records updated, plus 3155 records inactivated, plus 4411 records added, as expected as matches exactly with cut off QA report: https://dailybuild.ihtsdotools.org/qa-beta/ (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) DIFFERENT TO PUBLISHED RELEASE, which had following changes: 2476 records updated, plus 3142, records inactivated, plus 4411 records added HOWEVER, I THEN RAN A COMPARISON BETWEEN THE JULY MEMBER RELEASE + THE JULY OPTIONAL RELEASE, AND THE CONCEPT SNAPSHOT FILES MATCHED EXACTLY. Therefore the final result is the same (as expected), these slight differences above are clearly just highlighting a few differences between the Published Jan 2019 release + the Optional Jan 2019 release. | |
| Description files | 19546 | 108 records updated, plus 4076 records inactivated, plus 15362 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on ) DIFFERENT TO PUBLISHED RELEASE, which had following changes: 136 records updated, plus 4048 records inactivated, plus 15362 records added HOWEVER, I THEN RAN A COMPARISON BETWEEN THE JULY MEMBER RELEASE + THE JULY OPTIONAL RELEASE, AND THE DESCRIPTION SNAPSHOT FILES MATCHED EXACTLY. Therefore the final result is the same (as expected), these slight differences above are clearly just highlighting a few differences between the Published Jan 2019 release + the Optional Jan 2019 release. | |
| Relationship files | 114939 | 183 records updated, plus 49613 records inactivated, plus 65143 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) HOWEVER, RVF shows a couple of potential issues:
| |
| OwlExpression files | 37875 | 30300 records updated, plus 3142 records inactivated, plus 4433 records added Andrew Atkinson The total number of axioms would be at least 351038. There are 4411 new axioms and inactivations of 3142 axioms in the July 2019 release. It means that there are 1269 additional axioms comparing to 349769 in the last demo release. There were 224 axioms in the January release. The new axioms would be 350814. I guess those 20 axioms (350834-350814) would be GCIs and 'additional axioms'. I do not have access to the Alpha file to confirm. Why the number of impact is different to the new records? Yong - comments on Spot checked the following:
Also checked that the OPTIONAL OwlExpression Snapshot contains 354,202 records, BUT THE MEMBER RELEASE CONTAINS 351,060 - Why does the OPTIONAL Snapshot contain over 3000 more records than the published Member Snapshot???? Good news, this matches exactly to the number of Concept records inactivated in the latest July cycle (3142) , and Michael confirmed (Slack 12:53 17/07/2019) that we are creating Axioms for inactive concepts in the Optional release, but NOT in the Member/Public releases. This is because those 3142 records were active in the Jan 2019 Optional release, and so even though they've been inactived now they exist in the Optional Snapshot. HOWEVER, because they were inactviated BEFORE we created the final OWLAxiom refset for the PUBLIC July 2019 Release, we didn't want to create Axioms for already inactive concepts, so they'll never exist in the Public releases. Michael also signed off the new Optional Delta (Slack - 11:32 on Yong also signed off both OWLExpression Optional Delta + entire Optional release package by email at 10:00 on | |
| Stated Relationship files | 0 | 0 records updated, AS EXPECTED AS WE ALREADY INACTIVATED ALL OF THESE RECORDS IN JAN 2019, SO WE SHOULD HAVE A BLANK DELTA HERE (as confirmed by Michael on slack at 12:00 on | |
| TextDefinition files | 688 | 0 records updated, plus 25 records inactivated, plus 663 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on | |
| SimpleMap files | 4442 | 2 records inactivated, plus 4440 records added, as expected as: 4411 added for CTV3 (900000000000497000) (as part of the normal authoring cycle updates, exported from the termServer - this is the exact expected amount as it matches exactly the number of new concepts created in the latest authoring cycle) + 29 new + 2 inactivated records for ICD-0 as expected, matching the 31 records in the Delta from mapping tool. | |
| ExtendedMap files | 2056 | 25 records updated, plus 630 records inactivated, plus 1405 records added, as expected from the 2056 changes in the ICD-10 map Delta file that WCI sent us from the mapping tool export Same as International Published release, so looks good | |
| Simple Refset files | 104 | 0 records updated, plus 20 records inactivated, plus 84 records added, as expected from the Lateralizable Refset changes that Yong made in this cycle, exported in a Delta file from the Refset tool (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) Same as International Published release, so looks good | |
| ModuleDependency files | 3 | 3 records updated, as expected for July 2019 effectiveTimes | |
| Readme file | July 2019 dates updated + Alpha "x" prefixes added, as expected | ||
| MRCM Attribute Domain files | 11 | 5 Jan 2019 Published records (for Domain 373873005) inactivated, plus 5 July 2019 Beta records newly added (for Domain 781405001) to replace them, as expected in ISRS-564: < 03b4720d-5840-41d5-bcf4-884c603acc28 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 < 16965a9c-e4ba-4348-9b45-03150f74986c 20190731 1 900000000000012004 723561005 774161007 781405001 1 0..* 0..1 723597001 723596005 < b1bfe4c7-b443-45fa-9653-108093235e5a 20190731 1 900000000000012004 723561005 774160008 781405001 1 1..* 1..1 723597001 723596005 < f3a97490-6c74-404e-a3e9-436b7d4ca2a1 20190731 1 900000000000012004 723561005 774159003 781405001 0 0..1 0..0 723597001 723596005 < be279b7b-2331-496c-b3e6-51b94df106fc 20190731 1 900000000000012004 723561005 774163005 781405001 1 0..* 0..1 723597001 723596005 > 391f932e-3158-47bb-a95e-a2b1c19e864d 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 Plus 1 additional new record: > 07805dc4-f785-48f1-a7b0-b089b29f1c4e 20190731 1 900000000000012004 723561005 784276002 781405001 0 1..1 0..0 723597001 723596005d | |
| MRCM AttributeRange files | 12 | 2 records inactivated, plus < 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 2 new records added: > 5d65c8b2-f5e3-4445-8be3-2a0484962c2e 20190731 1 900000000000012004 723562003 411116001 << 736542009 |Pharmaceutical dose form (dose form)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 736542009 |Pharmaceutical dose form (dose form)| 723597001 723596005 > 3afe6bd3-16b5-4c19-a221-07c07f57f0ff 20190731 1 900000000000012004 723562003 784276002 < 260299005 |Number (qualifier value)| << 781405001 |Medicinal product package (product)|: [1..1] 784276002 |Count of clinical drug type| = < 260299005 |Number (qualifier value)| 723597001 723596005 Plus 7 updated in total These 2: < bdb62005-506f-4088-9bba-bedd410f23a3 20170731 1 900000000000012004 723562003 370131001 << 125676002 |Person (person)| OR << 35359004 |Family (social concept)| OR << 133928008 |Community (social concept)| OR << 105455006 |Donor for medical or surgical procedure (person)| OR << 389109008 |Group (social concept)| << 71388002 |Procedure (procedure)|: [0..*] { [0..1] 370131001 |Recipient category| = (<< 125676002 |Person (person)| OR << 35359004 |Family (social concept)| OR << 133928008 |Community (social concept)| OR << 105455006 |Donor for medical or surgical procedure (person)| OR << 389109008 |Group (social concept)|) } 723597001 723596005 < faf7265b-1290-40f1-ac73-d34d9a851939 20170731 1 900000000000012004 723562003 255234002 << 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)| (<< 404684003 |Clinical finding (finding)| OR << 272379006 |Event (event)|): [0..*] { [0..1] 255234002 |After| = (<< 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)|) } 723597001 723596005 -- + 5 records had the DomainID changed, as expected in ISRS-564 + "OR Medicinal product package (product)" clause removed from all records to correct erroneous Beta Version 1: < 2affaf44-9365-4d6d-84d3-31409206a77a 20190131 1 900000000000012004 723562003 774158006 << 774167006 | Product name (product name)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774158006 |Has product name| = << 774167006 | Product name (product name)| 723597001 723596005 < 355c9063-7238-4409-81a8-13f22b2a8bff 20190131 1 900000000000012004 723562003 774161007 < 260299005 |Number (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774161007 |Has pack size| = < 260299005 |Number (qualifier value)| } 723597001 723596005 < 608ab6f5-6830-4294-926a-5c3a20b62060 20190131 1 900000000000012004 723562003 774159003 << 774164004 | Supplier (supplier)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774159003 |Has supplier| = << 774164004 | Supplier (supplier)| 723597001 723596005 < e491647d-1793-4b20-b92d-c1180a96b00f 20190131 1 900000000000012004 723562003 774163005 << 767524001 |Unit of measure (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774163005 |Has pack size unit| = << 767524001 |Unit of measure (qualifier value)| } 723597001 723596005 < e5945adf-c075-4fb7-8f1b-515a124326cf 20190131 1 900000000000012004 723562003 774160008 << 763158003 |Medicinal product (product)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774160008 |Contains clinical drug| = << 763158003 |Medicinal product (product)| } 723597001 723596005 SOMEHOW different to published Internaitonal, so need to run a comparison between this optional package and the International published release to ensure the MRCM attribute Range files match... - BASICALLY LOOKS LIKE THE UUID'S WERE SOMEHOW SCREWEED UP, AS WE NOW HAVE A DUPLICATE RECORD IN THE OPTIONAL PACKAGE: 112642bb-9ead-460d-b080-72325ec40ef7 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 ********* NOT ACTUALLY DUPLICATE!! MINOR CHANGE from "[0..1]" to "[0..*]" The reason for this is the ID differences between the Jan 2019 PUBLISHED release, and the Jan 2019 OPTIONAL release - anything that didn't have a UUID already assigned to it (ie) NEW records in the Delta files in Jan 2019, will have had different ID's assigned to them in the Jan 2019 PUBLISHED release than they did in the Jan 2019 OPTIONAL release. For example this was the original Jan 2019 PUBLISHED record: 112642bb-9ead-460d-b080-72325ec40ef7 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 Whereas the Jan 2019 OPTIONAL record was identical, but with a different ID: 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 This meant that when this record got inactivated in July 2019 (with the ID 112642bb-9ead-460d-b080-72325ec40ef7 in the Delta), the Member release correctly reconciled it to the published record from the Jan 2019 PUBLISHED release. However, the OPTIONAL package never had that ID in it, and therefore it sets the inactivation record correctly, but KEEPS the OPTIONAL record (with ID 13d042db-a541-4c6f-98e5-a119706e916f) as well! Not much can be done about this, so we'll just have to call it out as a known issue in the OPTIONAL release - shouldn't be a huge issue as people should only really care about the OWLExpression files. NEED TO REPLACE THE UUID IN THE ACTIVATION RECORD IN THE DELTA (for the OPTIONAL package only) WITH THE UUID THAT WE PUBLISHED IN THE JAN 2019 OPTIONAL RELEASE PACKAGE ?????????? Matches International changes of 2 records inactivated + 6 added, as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) | |
| MRCM Domain files | 11 | 9 records updated, plus 1 inactivated, plus 1 new record added ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) Same as International published release | |
| Association Reference files | 6892 | 521 records updated, plus 1687 records inactivated, plus 4741 records added Yong confirmed that this is approximately the expected amount on There are 126 new additions and 24 inactivation for the 734138000|Anatomy structure and entire association reference set (foundation metadata concept)| Slightly different to International Published release, but only by a few records so looks good | |
| Attribute Value files | 16375 | 1396 records updated, plus 196 records inactivated, 14979 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on Slightly different to International Published release, but only by a few records so looks good | |
| Language refset files | 39699 | 1004 records updated, plus 7868 records inactivated, plus 30880 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on . Slightly different to International Published release, but only by a few records so looks good |
Production (July 2019 International Release OPTIONAL package (VERSION 3)) vs Production (July 2019 International Release OPTIONAL package) VERSION 4 traceability
Differences found in package Comparison | Number of records impacted | Rationale | |
|---|---|---|---|
| Relationship files | 22008 | 22008 ID changes only - is the UAT version picking up the right ID's now???? ****** NO IMPROVEMENT - NEED TO DECIDE IF IMPROVEMENTS REQUIRED TOMORROW AFTER CHECK RVF RESULTS.... ***** 183 records updated, pl 49613 records inactivated, plus 65143 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) HOWEVER, RVF shows a couple of potential issues:
| |
| OwlExpression files | 0 | ****** NO IMPROVEMENT NEEDED AS Version 2 HAD CLEAN OWLExpression FILE SIGNED OFF BY ALL (including Yong) INTERNALLY ****** | |
| Language files | 64 | 64 ID changes only - is the UAT version picking up the right ID's now???? | |
| SimpleMap files | 835 | 835 records had their maps changed??!!!! As expected ????????? (is this because we ran it against UAT - maybe need to update the S3 externallyMaintained repo in S3 with latest Prod Delta's??) NO - double checked and both Delta's are identical - more likely an issue with the CTV3 record creation/maintenance in UAT vs Production?? NEED TO CHECK AGAINST THE ORIGINAL JAN 2019 RELEASE NOW AND SEE IF CHANGES THERE ARE EXPECTED?? (as if Jan 2019 vs new UAT July 2019 has the expected number/type of changes, then it's irrelevant what the comparison between UAT July 2019 and Prod July 2019 comes back with) | |
| MRCM AttributeDomain files | 5 | 5 ID changes only - is the UAT version picking up the right ID's now???? |
Production (July 2019 International Release OPTIONAL package (VERSION 2)) vs Production (July 2019 International Release OPTIONAL package) VERSION 3 traceability
Differences found in package Comparison | Number of records impacted | Rationale | |
|---|---|---|---|
| Relationship files | 0 | ****** NO IMPROVEMENT - NEED TO DECIDE IF IMPROVEMENTS REQUIRED TOMORROW AFTER CHECK RVF RESULTS.... ***** 183 records updated, plus 49613 records inactivated, plus 65143 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) HOWEVER, RVF shows a couple of potential issues:
| |
| OwlExpression files | 0 | ****** NO IMPROVEMENT NEEDED AS Version 2 HAD CLEAN OWLExpression FILE SIGNED OFF BY ALL (including Yong) INTERNALLY ****** | |
| Stated Relationship files | 1701361 | 0 records updated, plus 1701361 records inactivated, plus 0 records added (no data on this from qa.snomed.org) - Yong confirmed that this is the expected amount on WRONG, AS WE ALREADY INACTIVATED ALL OF THESE RECORDS IN JAN 2019, SO WE SHOULD HAVE A BLANK DELTA HERE (as confirmed by Michael on slack at 12:00 on THINK THIS JUST REVERTED THE SAME ORIGINAL DATA DUE TO WIPING THE STATED DELTA AND REBUILDING - Sounds okay now but need to compare to Member Release... Tried that, BUT the problem is that the effectiveTimes are all different! So the comparison program shows nearly all records changed, but this is just because the Optional package has all the inactivation records set to 20190131, and the Member release set to 20190731!! | |
| SimpleMap files | 4411 | 4411 added for CTV3 (as part of the normal authoring cycle updates, exported from the termServer - this is the exact expected amount as it matches exactly the number of new concepts created in the latest authoring cycle) as expected as same as the International Edition | |
| MRCM AttributeRange files | 1 | Following DUPLICATE RECORD removed from the OPTIONAL PACKAGE: 112642bb-9ead-460d-b080-72325ec40ef7 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 Following record also removed from Snapshot, as expected (as now inactivated): 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 Plus, the correct inactivation record (with the UUID consistent with the Jan 2019 Optional Release package) added in: > 13d042db-a541-4c6f-98e5-a119706e916f 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 |
Production (January 2019 International Release OPTIONAL package (PUBLISHED)) vs Production (July 2019 International Release OPTIONAL package) VERSION 2 traceability
Differences found in package Comparison | Number of records impacted | Rationale | |
|---|---|---|---|
| RefsetDescriptor files | 1 | 1 record updated with the new attributeType ("URL" instead of "parsable string), as expected in ISRS-583: < a87a81a3-b10c-490b-9cc1-d94fafc5dc27 20170731 1 900000000000012004 900000000000456007 723560006 723570008 707000009 7 Same as International published release | |
| Concept files | 10029 | 2463 records updated, plus 3155 records inactivated, plus 4411 records added, as expected as matches exactly with cut off QA report: https://dailybuild.ihtsdotools.org/qa-beta/ (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) DIFFERENT TO PUBLISHED RELEASE, which had following changes: 2476 records updated, plus 3142, records inactivated, plus 4411 records added HOWEVER, I THEN RAN A COMPARISON BETWEEN THE JULY MEMBER RELEASE + THE JULY OPTIONAL RELEASE, AND THE CONCEPT SNAPSHOT FILES MATCHED EXACTLY. Therefore the final result is the same (as expected), these slight differences above are clearly just highlighting a few differences between the Published Jan 2019 release + the Optional Jan 2019 release. | |
| Description files | 19546 | 108 records updated, plus 4076 records inactivated, plus 15362 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on ) DIFFERENT TO PUBLISHED RELEASE, which had following changes: 136 records updated, plus 4048 records inactivated, plus 15362 records added HOWEVER, I THEN RAN A COMPARISON BETWEEN THE JULY MEMBER RELEASE + THE JULY OPTIONAL RELEASE, AND THE DESCRIPTION SNAPSHOT FILES MATCHED EXACTLY. Therefore the final result is the same (as expected), these slight differences above are clearly just highlighting a few differences between the Published Jan 2019 release + the Optional Jan 2019 release. | |
| Relationship files | 114939 | 183 records updated, plus 49613 records inactivated, plus 65143 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) HOWEVER, RVF shows a couple of potential issues:
| |
| OwlExpression files | 37875 | 30300 records updated, plus 3142 records inactivated, plus 4433 records added Andrew Atkinson The total number of axioms would be at least 351038. There are 4411 new axioms and inactivations of 3142 axioms in the July 2019 release. It means that there are 1269 additional axioms comparing to 349769 in the last demo release. There were 224 axioms in the January release. The new axioms would be 350814. I guess those 20 axioms (350834-350814) would be GCIs and 'additional axioms'. I do not have access to the Alpha file to confirm. Why the number of impact is different to the new records? Yong - comments on Spot checked the following:
Also checked that the OPTIONAL OwlExpression Snapshot contains 354,202 records, BUT THE MEMBER RELEASE CONTAINS 351,060 - Why does the OPTIONAL Snapshot contain over 3000 more records than the published Member Snapshot???? Good news, this matches exactly to the number of Concept records inactivated in the latest July cycle (3142) , and Michael confirmed (Slack 12:53 17/07/2019) that we are creating Axioms for inactive concepts in the Optional release, but NOT in the Member/Public releases. This is because those 3142 records were active in the Jan 2019 Optional release, and so even though they've been inactived now they exist in the Optional Snapshot. HOWEVER, because they were inactviated BEFORE we created the final OWLAxiom refset for the PUBLIC July 2019 Release, we didn't want to create Axioms for already inactive concepts, so they'll never exist in the Public releases. Michael also signed off the new Optional Delta (Slack - 11:32 on Yong also signed off both OWLExpression Optional Delta + entire Optional release package by email at 10:00 on | |
| Stated Relationship files | 1701361 | 0 records updated, plus 1701361 records inactivated, plus 0 records added (no data on this from qa.snomed.org) - Yong confirmed that this is the expected amount on WRONG, AS WE ALREADY INACTIVATED ALL OF THESE RECORDS IN JAN 2019, SO WE SHOULD HAVE A BLANK DELTA HERE (as confirmed by Michael on slack at 12:00 on NEED TO WIPE THE STATED DELTA AND REBUILD | |
| TextDefinition files | 688 | 0 records updated, plus 25 records inactivated, plus 663 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on | |
| SimpleMap files | 31 | 2 records inactivated, plus 29 records added for ICD-0 as expected, matching the 31 records in the Delta from mapping tool. ******** BUT NO SIGN OF THE 4411 added for CTV3 (as part of the normal authoring cycle updates, exported from the termServer - this is the exact expected amount as it matches exactly the number of new concepts created in the latest authoring cycle) IN THE INTERNATIONAL EDITION!!!! Also backed up by the RVF failure "bab42070-7f25-11e1-b0c4-0800200c9a66": https://rvf.ihtsdotools.org/api/result/1562322036701?storageLocation=international/snomed_ct_international_edition_july_2019_complete_owl_file_demonstration_release_package/2019-07-05T09:45:00 This is because the "createLegacyIDs" flag was set to false for the Optional release for some reason - therefore need to update it and rebuild | |
| ExtendedMap files | 2056 | 25 records updated, plus 626 records inactivated, plus 1405 records added, as expected from the 2056 changes in the ICD-10 map Delta file that WCI sent us from the mapping tool export Same as International Published release, so looks good | |
| Simple Refset files | 104 | 0 records updated, plus 20 records inactivated, plus 84 records added, as expected from the Lateralizable Refset changes that Yong made in this cycle, exported in a Delta file from the Refset tool (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) Same as International Published release, so looks good | |
| ModuleDependency files | 3 | 3 records updated, as expected for July 2019 effectiveTimes | |
| Readme file | July 2019 dates updated + Alpha "x" prefixes added, as expected | ||
| MRCM Attribute Domain files | 10 | 5 Jan 2019 Published records (for Domain 373873005) inactivated, plus 5 July 2019 Beta records newly added (for Domain 781405001) to replace them, as expected in ISRS-564: < 03b4720d-5840-41d5-bcf4-884c603acc28 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 < 16965a9c-e4ba-4348-9b45-03150f74986c 20190731 1 900000000000012004 723561005 774161007 781405001 1 0..* 0..1 723597001 723596005 < b1bfe4c7-b443-45fa-9653-108093235e5a 20190731 1 900000000000012004 723561005 774160008 781405001 1 1..* 1..1 723597001 723596005 < f3a97490-6c74-404e-a3e9-436b7d4ca2a1 20190731 1 900000000000012004 723561005 774159003 781405001 0 0..1 0..0 723597001 723596005 < be279b7b-2331-496c-b3e6-51b94df106fc 20190731 1 900000000000012004 723561005 774163005 781405001 1 0..* 0..1 723597001 723596005 > 391f932e-3158-47bb-a95e-a2b1c19e864d 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 Plus 1 additional new record: > 07805dc4-f785-48f1-a7b0-b089b29f1c4e 20190731 1 900000000000012004 723561005 784276002 781405001 0 1..1 0..0 723597001 723596005d | |
| MRCM AttributeRange files | 12 | 2 records inactivated, plus < 4c177f0d-03bc-4f5f-b0f9-e792467e652b 20180731 1 900000000000012004 723562003 411116001 << 736542009 |Pharmaceutical dose form (dose form)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 736542009 |Pharmaceutical dose form (dose form)| 723598006 723596005 > 112642bb-9ead-460d-b080-72325ec40ef7 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 3 new records added: > 5d65c8b2-f5e3-4445-8be3-2a0484962c2e 20190731 1 900000000000012004 723562003 411116001 << 736542009 |Pharmaceutical dose form (dose form)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 736542009 |Pharmaceutical dose form (dose form)| 723597001 723596005 > 3afe6bd3-16b5-4c19-a221-07c07f57f0ff 20190731 1 900000000000012004 723562003 784276002 < 260299005 |Number (qualifier value)| << 781405001 |Medicinal product package (product)|: [1..1] 784276002 |Count of clinical drug type| = < 260299005 |Number (qualifier value)| 723597001 723596005 Plus 7 updated in total These 2: < bdb62005-506f-4088-9bba-bedd410f23a3 20170731 1 900000000000012004 723562003 370131001 << 125676002 |Person (person)| OR << 35359004 |Family (social concept)| OR << 133928008 |Community (social concept)| OR << 105455006 |Donor for medical or surgical procedure (person)| OR << 389109008 |Group (social concept)| << 71388002 |Procedure (procedure)|: [0..*] { [0..1] 370131001 |Recipient category| = (<< 125676002 |Person (person)| OR << 35359004 |Family (social concept)| OR << 133928008 |Community (social concept)| OR << 105455006 |Donor for medical or surgical procedure (person)| OR << 389109008 |Group (social concept)|) } 723597001 723596005 < faf7265b-1290-40f1-ac73-d34d9a851939 20170731 1 900000000000012004 723562003 255234002 << 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)| (<< 404684003 |Clinical finding (finding)| OR << 272379006 |Event (event)|): [0..*] { [0..1] 255234002 |After| = (<< 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)|) } 723597001 723596005 -- + 5 records had the DomainID changed, as expected in ISRS-564 + "OR Medicinal product package (product)" clause removed from all records to correct erroneous Beta Version 1: < 2affaf44-9365-4d6d-84d3-31409206a77a 20190131 1 900000000000012004 723562003 774158006 << 774167006 | Product name (product name)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774158006 |Has product name| = << 774167006 | Product name (product name)| 723597001 723596005 < 355c9063-7238-4409-81a8-13f22b2a8bff 20190131 1 900000000000012004 723562003 774161007 < 260299005 |Number (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774161007 |Has pack size| = < 260299005 |Number (qualifier value)| } 723597001 723596005 < 608ab6f5-6830-4294-926a-5c3a20b62060 20190131 1 900000000000012004 723562003 774159003 << 774164004 | Supplier (supplier)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774159003 |Has supplier| = << 774164004 | Supplier (supplier)| 723597001 723596005 < e491647d-1793-4b20-b92d-c1180a96b00f 20190131 1 900000000000012004 723562003 774163005 << 767524001 |Unit of measure (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774163005 |Has pack size unit| = << 767524001 |Unit of measure (qualifier value)| } 723597001 723596005 < e5945adf-c075-4fb7-8f1b-515a124326cf 20190131 1 900000000000012004 723562003 774160008 << 763158003 |Medicinal product (product)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774160008 |Contains clinical drug| = << 763158003 |Medicinal product (product)| } 723597001 723596005 SOMEHOW different to published Internaitonal, so need to run a comparison between this optional package and the International published release to ensure the MRCM attribute Range files match... - BASICALLY LOOKS LIKE THE UUID'S WERE SOMEHOW SCREWEED UP, AS WE NOW HAVE A DUPLICATE RECORD IN THE OPTIONAL PACKAGE: 112642bb-9ead-460d-b080-72325ec40ef7 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 ********* NOT ACTUALLY DUPLICATE!! MINOR CHANGE from "[0..1]" to "[0..*]" The reason for this is the ID differences between the Jan 2019 PUBLISHED release, and the Jan 2019 OPTIONAL release - anything that didn't have a UUID already assigned to it (ie) NEW records in the Delta files in Jan 2019, will have had different ID's assigned to them in the Jan 2019 PUBLISHED release than they did in the Jan 2019 OPTIONAL release. For example this was the original Jan 2019 PUBLISHED record: 112642bb-9ead-460d-b080-72325ec40ef7 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 Whereas the Jan 2019 OPTIONAL record was identical, but with a different ID: 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 This meant that when this record got inactivated in July 2019 (with the ID 112642bb-9ead-460d-b080-72325ec40ef7 in the Delta), the Member release correctly reconciled it to the published record from the Jan 2019 PUBLISHED release. However, the OPTIONAL package never had that ID in it, and therefore it sets the inactivation record correctly, but KEEPS the OPTIONAL record (with ID 13d042db-a541-4c6f-98e5-a119706e916f) as well! Not much can be done about this, so we'll just have to call it out as a known issue in the OPTIONAL release - shouldn't be a huge issue as people should only really care about the OWLExpression files. NEED TO REPLACE THE UUID IN THE ACTIVATION RECORD IN THE DELTA (for the OPTIONAL package only) WITH THE UUID THAT WE PUBLISHED IN THE JAN 2019 OPTIONAL RELEASE PACKAGE ?????????? Matches International changes of 2 records inactivated + 6 added, as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) | |
| MRCM Domain files | 11 | 9 records updated, plus 1 inactivated, plus 1 new record added ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) Same as International published release | |
| Association Reference files | 6892 | 521 records updated, plus 1687 records inactivated, plus 4741 records added Yong confirmed that this is approximately the expected amount on There are 126 new additions and 24 inactivation for the 734138000|Anatomy structure and entire association reference set (foundation metadata concept)| Slightly different to International Published release, but only by a few records so looks good | |
| Attribute Value files | 16375 | 1396 records updated, plus 176 records inactivated, 14979 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on Slightly different to International Published release, but only by a few records so looks good | |
| Language refset files | 39699 | 1004 records updated, plus 8819 records inactivated, plus 30880 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on . Slightly different to International Published release, but only by a few records so looks good |
Production (January 2019 International Release OPTIONAL package (PUBLISHED)) vs Production (July 2019 International Release OPTIONAL package) VERSION 1 traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| RefsetDescriptor files | 1 | 1 record updated with the new attributeType ("URL" instead of "parsable string), as expected in ISRS-583: < a87a81a3-b10c-490b-9cc1-d94fafc5dc27 20170731 1 900000000000012004 900000000000456007 723560006 723570008 707000009 7 Same as International published release | |
| Concept files | 10029 | 2476 records updated, plus 3142, records inactivated, plus 4411 records added, as expected as matches exactly with cut off QA report: https://dailybuild.ihtsdotools.org/qa-beta/ (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) | |
| Description files | 19546 | 136 records updated, plus 4048 records inactivated, plus 15362 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on ) | |
| Relationship files | 259183 | 147216 records updated, plus 45783 records inactivated, plus 57019 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) | |
| OwlExpression files | 350827 | 349545 records REMOVED, NOT EXPECTED AS SHOULD BE A CONTINUATION OF THE JAN 2019 RELEASE!! Andrew Atkinson The total number of axioms would be at least 351038. There are 4411 new axioms and inactivations of 3142 axioms in the July 2019 release. It means that there are 1269 additional axioms comparing to 349769 in the last demo release. There were 224 axioms in the January release. The new axioms would be 350814. I guess those 20 axioms (350834-350814) would be GCIs and 'additional axioms'. I do not have access to the Alpha file to confirm. Why the number of impact is different to the new records? Yong - comments on | |
| Stated Relationship files | 814884 | 0 records updated, plus 814884 records inactivated, plus 0 records added (no data on this from qa.snomed.org) - Yong confirmed that this is the expected amount on | |
| TextDefinition files | 688 | 0 records updated, plus 25 records inactivated, plus 663 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on | |
| SimpleMap files | 11934 4442 | 11905 records updated, plus 2 records inactivated, plus 29 records added TOTALLY DIFFERENT TO INTERNATIONAL EDITION! 0 records updated, plus 2 records inactivated, plus 4440 records added, as expected as: 4411 added for CTV3 (as part of the normal authoring cycle updates, exported from the termServer - this is the exact expected amount as it matches exactly the number of new concepts created in the latest authoring cycle) + 31 new/updated records for ICD-0 as expected, matching the 31 records in the Delta from mapping tool. | |
| ExtendedMap files | 2056 | 25 records updated, plus 626 records inactivated, plus 1405 records added, as expected from the 2056 changes in the ICD-10 map Delta file that WCI sent us from the mapping tool export Same as International Published release, so looks good | |
| Simple Refset files | 104 | 0 records updated, plus 20 records inactivated, plus 84 records added, as expected from the Lateralizable Refset changes that Yong made in this cycle, exported in a Delta file from the Refset tool (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) Same as International Published release, so looks good | |
| ModuleDependency files | 3 | 3 records updated, as expected for July 2019 effectiveTimes | |
| Readme file | July 2019 dates updated + Alpha "x" prefixes added, as expected | ||
| MRCM Attribute Domain files | 10 | 5 Jan 2019 Published records (for Domain 373873005) inactivated, plus 5 July 2019 Beta records newly added (for Domain 781405001) to replace them, as expected in ISRS-564: < 03b4720d-5840-41d5-bcf4-884c603acc28 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 < 16965a9c-e4ba-4348-9b45-03150f74986c 20190731 1 900000000000012004 723561005 774161007 781405001 1 0..* 0..1 723597001 723596005 < b1bfe4c7-b443-45fa-9653-108093235e5a 20190731 1 900000000000012004 723561005 774160008 781405001 1 1..* 1..1 723597001 723596005 < f3a97490-6c74-404e-a3e9-436b7d4ca2a1 20190731 1 900000000000012004 723561005 774159003 781405001 0 0..1 0..0 723597001 723596005 < be279b7b-2331-496c-b3e6-51b94df106fc 20190731 1 900000000000012004 723561005 774163005 781405001 1 0..* 0..1 723597001 723596005 > 391f932e-3158-47bb-a95e-a2b1c19e864d 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 Plus 1 additional new record: > 07805dc4-f785-48f1-a7b0-b089b29f1c4e 20190731 1 900000000000012004 723561005 784276002 781405001 0 1..1 0..0 723597001 723596005d | |
| MRCM AttributeRange files | 6 | 2 records inactivated, plus 0 updated, plus 2 new records added, ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) + 5 records had the DomainID changed, as expected in ISRS-564 + "OR Medicinal product package (product)" clause removed from all records to correct erroneous Beta Version 1: < 2affaf44-9365-4d6d-84d3-31409206a77a 20190131 1 900000000000012004 723562003 774158006 << 774167006 | Product name (product name)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774158006 |Has product name| = << 774167006 | Product name (product name)| 723597001 723596005 < 355c9063-7238-4409-81a8-13f22b2a8bff 20190131 1 900000000000012004 723562003 774161007 < 260299005 |Number (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774161007 |Has pack size| = < 260299005 |Number (qualifier value)| } 723597001 723596005 < 608ab6f5-6830-4294-926a-5c3a20b62060 20190131 1 900000000000012004 723562003 774159003 << 774164004 | Supplier (supplier)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774159003 |Has supplier| = << 774164004 | Supplier (supplier)| 723597001 723596005 < e491647d-1793-4b20-b92d-c1180a96b00f 20190131 1 900000000000012004 723562003 774163005 << 767524001 |Unit of measure (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774163005 |Has pack size unit| = << 767524001 |Unit of measure (qualifier value)| } 723597001 723596005 < e5945adf-c075-4fb7-8f1b-515a124326cf 20190131 1 900000000000012004 723562003 774160008 << 763158003 |Medicinal product (product)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774160008 |Contains clinical drug| = << 763158003 |Medicinal product (product)| } 723597001 723596005 SLightly different to published Internaitonal, so need to run a comparison between this optional package and the International published release to ensure the MRCM attribute Range files match... | |
| MRCM Domain files | 11 | 9 records updated, plus 1 inactivated, plus 1 new record added ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) Same as International published release | |
| Association Reference files | 6892 | 521 records updated, plus 1687 records inactivated, plus 4741 records added Yong confirmed that this is approximately the expected amount on There are 126 new additions and 24 inactivation for the 734138000|Anatomy structure and entire association reference set (foundation metadata concept)| Slightly different to International Published release, but only by a few records so looks good | |
| Attribute Value files | 16375 | 1396 records updated, plus 176 records inactivated, 14979 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on Slightly different to International Published release, but only by a few records so looks good | |
| Language refset files | 39699 | 1004 records updated, plus 8819 records inactivated, plus 30880 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on . Slightly different to International Published release, but only by a few records so looks good |
Production (January 2019 International Release OPTIONAL package (PUBLISHED)) vs Production (July 2019 International Release OPTIONAL package) VERSION 2 traceability
Differences found in package Comparison | Number of records impacted | Rationale | |
|---|---|---|---|
| RefsetDescriptor files | 1 | 1 record updated with the new attributeType ("URL" instead of "parsable string), as expected in ISRS-583: < a87a81a3-b10c-490b-9cc1-d94fafc5dc27 20170731 1 900000000000012004 900000000000456007 723560006 723570008 707000009 7 Same as International published release | |
| Concept files | 10029 | 2463 records updated, plus 3155 records inactivated, plus 4411 records added, as expected as matches exactly with cut off QA report: https://dailybuild.ihtsdotools.org/qa-beta/ (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) | |
| Description files | 19546 | 108 records updated, plus 4076 records inactivated, plus 15362 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on ) | |
| Relationship files | 114939 | 183 records updated, plus 49613 records inactivated, plus 65143 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) | |
| OwlExpression files | 350827 | 183 records updated, plus 49613 records inactivated, plus 65143 records added Andrew Atkinson The total number of axioms would be at least 351038. There are 4411 new axioms and inactivations of 3142 axioms in the July 2019 release. It means that there are 1269 additional axioms comparing to 349769 in the last demo release. There were 224 axioms in the January release. The new axioms would be 350814. I guess those 20 axioms (350834-350814) would be GCIs and 'additional axioms'. I do not have access to the Alpha file to confirm. Why the number of impact is different to the new records? Yong - comments on | |
| Stated Relationship files | 814884 | 0 records updated, plus 814884 records inactivated, plus 0 records added (no data on this from qa.snomed.org) - Yong confirmed that this is the expected amount on | |
| TextDefinition files | 688 | 0 records updated, plus 25 records inactivated, plus 663 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on | |
| SimpleMap files | 31 | 2 records inactivated, plus 29 records added for ICD-0 as expected, matching the 31 records in the Delta from mapping tool. ******** BUT NO SIGN OF THE 4411 added for CTV3 (as part of the normal authoring cycle updates, exported from the termServer - this is the exact expected amount as it matches exactly the number of new concepts created in the latest authoring cycle) IN THE INTERNATIONAL EDITION!!!! This is because the "createLegacyIDs" flag was set to false for the Optional release for some reason - therefore need to update it and rebuild | |
| ExtendedMap files | 2056 | 25 records updated, plus 626 records inactivated, plus 1405 records added, as expected from the 2056 changes in the ICD-10 map Delta file that WCI sent us from the mapping tool export Same as International Published release, so looks good | |
| Simple Refset files | 104 | 0 records updated, plus 20 records inactivated, plus 84 records added, as expected from the Lateralizable Refset changes that Yong made in this cycle, exported in a Delta file from the Refset tool (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) Same as International Published release, so looks good | |
| ModuleDependency files | 3 | 3 records updated, as expected for July 2019 effectiveTimes | |
| Readme file | July 2019 dates updated + Alpha "x" prefixes added, as expected | ||
| MRCM Attribute Domain files | 10 | 5 Jan 2019 Published records (for Domain 373873005) inactivated, plus 5 July 2019 Beta records newly added (for Domain 781405001) to replace them, as expected in ISRS-564: < 03b4720d-5840-41d5-bcf4-884c603acc28 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 < 16965a9c-e4ba-4348-9b45-03150f74986c 20190731 1 900000000000012004 723561005 774161007 781405001 1 0..* 0..1 723597001 723596005 < b1bfe4c7-b443-45fa-9653-108093235e5a 20190731 1 900000000000012004 723561005 774160008 781405001 1 1..* 1..1 723597001 723596005 < f3a97490-6c74-404e-a3e9-436b7d4ca2a1 20190731 1 900000000000012004 723561005 774159003 781405001 0 0..1 0..0 723597001 723596005 < be279b7b-2331-496c-b3e6-51b94df106fc 20190731 1 900000000000012004 723561005 774163005 781405001 1 0..* 0..1 723597001 723596005 > 391f932e-3158-47bb-a95e-a2b1c19e864d 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 Plus 1 additional new record: > 07805dc4-f785-48f1-a7b0-b089b29f1c4e 20190731 1 900000000000012004 723561005 784276002 781405001 0 1..1 0..0 723597001 723596005d | |
| MRCM AttributeRange files | 12 | 2 records inactivated, plus < 4c177f0d-03bc-4f5f-b0f9-e792467e652b 20180731 1 900000000000012004 723562003 411116001 << 736542009 |Pharmaceutical dose form (dose form)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 736542009 |Pharmaceutical dose form (dose form)| 723598006 723596005 > 112642bb-9ead-460d-b080-72325ec40ef7 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 3 new records added: > 5d65c8b2-f5e3-4445-8be3-2a0484962c2e 20190731 1 900000000000012004 723562003 411116001 << 736542009 |Pharmaceutical dose form (dose form)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 736542009 |Pharmaceutical dose form (dose form)| 723597001 723596005 > 3afe6bd3-16b5-4c19-a221-07c07f57f0ff 20190731 1 900000000000012004 723562003 784276002 < 260299005 |Number (qualifier value)| << 781405001 |Medicinal product package (product)|: [1..1] 784276002 |Count of clinical drug type| = < 260299005 |Number (qualifier value)| 723597001 723596005 Plus 7 updated in total These 2: < bdb62005-506f-4088-9bba-bedd410f23a3 20170731 1 900000000000012004 723562003 370131001 << 125676002 |Person (person)| OR << 35359004 |Family (social concept)| OR << 133928008 |Community (social concept)| OR << 105455006 |Donor for medical or surgical procedure (person)| OR << 389109008 |Group (social concept)| << 71388002 |Procedure (procedure)|: [0..*] { [0..1] 370131001 |Recipient category| = (<< 125676002 |Person (person)| OR << 35359004 |Family (social concept)| OR << 133928008 |Community (social concept)| OR << 105455006 |Donor for medical or surgical procedure (person)| OR << 389109008 |Group (social concept)|) } 723597001 723596005 < faf7265b-1290-40f1-ac73-d34d9a851939 20170731 1 900000000000012004 723562003 255234002 << 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)| (<< 404684003 |Clinical finding (finding)| OR << 272379006 |Event (event)|): [0..*] { [0..1] 255234002 |After| = (<< 404684003 |Clinical finding (finding)| OR << 71388002 |Procedure (procedure)|) } 723597001 723596005 -- + 5 records had the DomainID changed, as expected in ISRS-564 + "OR Medicinal product package (product)" clause removed from all records to correct erroneous Beta Version 1: < 2affaf44-9365-4d6d-84d3-31409206a77a 20190131 1 900000000000012004 723562003 774158006 << 774167006 | Product name (product name)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774158006 |Has product name| = << 774167006 | Product name (product name)| 723597001 723596005 < 355c9063-7238-4409-81a8-13f22b2a8bff 20190131 1 900000000000012004 723562003 774161007 < 260299005 |Number (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774161007 |Has pack size| = < 260299005 |Number (qualifier value)| } 723597001 723596005 < 608ab6f5-6830-4294-926a-5c3a20b62060 20190131 1 900000000000012004 723562003 774159003 << 774164004 | Supplier (supplier)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774159003 |Has supplier| = << 774164004 | Supplier (supplier)| 723597001 723596005 < e491647d-1793-4b20-b92d-c1180a96b00f 20190131 1 900000000000012004 723562003 774163005 << 767524001 |Unit of measure (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774163005 |Has pack size unit| = << 767524001 |Unit of measure (qualifier value)| } 723597001 723596005 < e5945adf-c075-4fb7-8f1b-515a124326cf 20190131 1 900000000000012004 723562003 774160008 << 763158003 |Medicinal product (product)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774160008 |Contains clinical drug| = << 763158003 |Medicinal product (product)| } 723597001 723596005 SOMEHOW different to published Internaitonal, so need to run a comparison between this optional package and the International published release to ensure the MRCM attribute Range files match... - BASICALLY LOOKS LIKE THE UUID'S WERE SOMEHOW SCREWEED UP, AS WE NOW HAVE A DUPLICATE RECORD IN THE OPTIONAL PACKAGE: 112642bb-9ead-460d-b080-72325ec40ef7 20190731 0 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 ********* NOT ACTUALLY DUPLICATE!! MINOR CHANGE from "[0..1]" to "[0..*]" The reason for this is the ID differences between the Jan 2019 PUBLISHED release, and the Jan 2019 OPTIONAL release - anything that didn't have a UUID already assigned to it (ie) NEW records in the Delta files in Jan 2019, will have had different ID's assigned to them in the Jan 2019 PUBLISHED release than they did in the Jan 2019 OPTIONAL release. For example this was the original Jan 2019 PUBLISHED record: 112642bb-9ead-460d-b080-72325ec40ef7 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 Whereas the Jan 2019 OPTIONAL record was identical, but with a different ID: 13d042db-a541-4c6f-98e5-a119706e916f 20190131 1 900000000000012004 723562003 411116001 << 105904009 |Type of drug preparation (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] 411116001 |Has manufactured dose form| = << 105904009 |Type of drug preparation (qualifier value)| 723597001 723596005 This meant that when this record got inactivated in July 2019 (with the ID 112642bb-9ead-460d-b080-72325ec40ef7 in the Delta), the Member release correctly reconciled it to the published record from the Jan 2019 PUBLISHED release. However, the OPTIONAL package never had that ID in it, and therefore it sets the inactivation record correctly, but KEEPS the OPTIONAL record (with ID 13d042db-a541-4c6f-98e5-a119706e916f) as well! Not much can be done about this, so we'll just have to call it out as a known issue in the OPTIONAL release - shouldn't be a huge issue as people should only really care about the OWLExpression files. ?????????? Matches International changes of 2 records inactivated + 6 added, as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) | |
| MRCM Domain files | 11 | 9 records updated, plus 1 inactivated, plus 1 new record added ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) Same as International published release | |
| Association Reference files | 6892 | 521 records updated, plus 1687 records inactivated, plus 4741 records added Yong confirmed that this is approximately the expected amount on There are 126 new additions and 24 inactivation for the 734138000|Anatomy structure and entire association reference set (foundation metadata concept)| Slightly different to International Published release, but only by a few records so looks good | |
| Attribute Value files | 16375 | 1396 records updated, plus 176 records inactivated, 14979 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on Slightly different to International Published release, but only by a few records so looks good | |
| Language refset files | 39699 | 1004 records updated, plus 8819 records inactivated, plus 30880 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on . Slightly different to International Published release, but only by a few records so looks good |
Production (January 2019 International Release OPTIONAL package (PUBLISHED)) vs Production (July 2019 International Release OPTIONAL package) VERSION 1 traceability
Differences found in package Comparison | Number of RF2 records impacted | Related JIRA ticket(s) | Rationale |
|---|---|---|---|
| RefsetDescriptor files | 1 | 1 record updated with the new attributeType ("URL" instead of "parsable string), as expected in ISRS-583: < a87a81a3-b10c-490b-9cc1-d94fafc5dc27 20170731 1 900000000000012004 900000000000456007 723560006 723570008 707000009 7 Same as International published release | |
| Concept files | 10029 | 2476 records updated, plus 3142, records inactivated, plus 4411 records added, as expected as matches exactly with cut off QA report: https://dailybuild.ihtsdotools.org/qa-beta/ (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) | |
| Description files | 19546 | 136 records updated, plus 4048 records inactivated, plus 15362 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on ) | |
| Relationship files | 259183 | 147216 records updated, plus 45783 records inactivated, plus 57019 records added (no data on this from qa.snomed.org) - Andrew Atkinson , there are some differences for inactivated relationships (45,295) and new additions (65,633) and I am not sure about total number for updated records. Yong - comments on ) | |
| OwlExpression files | 350827 | 349545 records REMOVED, NOT EXPECTED AS SHOULD BE A CONTINUATION OF THE JAN 2019 RELEASE!! Andrew Atkinson The total number of axioms would be at least 351038. There are 4411 new axioms and inactivations of 3142 axioms in the July 2019 release. It means that there are 1269 additional axioms comparing to 349769 in the last demo release. There were 224 axioms in the January release. The new axioms would be 350814. I guess those 20 axioms (350834-350814) would be GCIs and 'additional axioms'. I do not have access to the Alpha file to confirm. Why the number of impact is different to the new records? Yong - comments on | |
| Stated Relationship files | 814884 | 0 records updated, plus 814884 records inactivated, plus 0 records added (no data on this from qa.snomed.org) - Yong confirmed that this is the expected amount on | |
| TextDefinition files | 688 | 0 records updated, plus 25 records inactivated, plus 663 records added (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on | |
| SimpleMap files | 11934 4442 | 11905 records updated, plus 2 records inactivated, plus 29 records added TOTALLY DIFFERENT TO INTERNATIONAL EDITION! 0 records updated, plus 2 records inactivated, plus 4440 records added, as expected as: 4411 added for CTV3 (as part of the normal authoring cycle updates, exported from the termServer - this is the exact expected amount as it matches exactly the number of new concepts created in the latest authoring cycle) + 31 new/updated records for ICD-0 as expected, matching the 31 records in the Delta from mapping tool. | |
| ExtendedMap files | 2056 | 25 records updated, plus 626 records inactivated, plus 1405 records added, as expected from the 2056 changes in the ICD-10 map Delta file that WCI sent us from the mapping tool export Same as International Published release, so looks good | |
| Simple Refset files | 104 | 0 records updated, plus 20 records inactivated, plus 84 records added, as expected from the Lateralizable Refset changes that Yong made in this cycle, exported in a Delta file from the Refset tool (plus confirmed by Maria to be as expected in her email at 08:40 on 23/05/2019) Same as International Published release, so looks good | |
| ModuleDependency files | 3 | 3 records updated, as expected for July 2019 effectiveTimes | |
| Readme file | July 2019 dates updated + Alpha "x" prefixes added, as expected | ||
| MRCM Attribute Domain files | 10 | 5 Jan 2019 Published records (for Domain 373873005) inactivated, plus 5 July 2019 Beta records newly added (for Domain 781405001) to replace them, as expected in ISRS-564: < 03b4720d-5840-41d5-bcf4-884c603acc28 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 < 16965a9c-e4ba-4348-9b45-03150f74986c 20190731 1 900000000000012004 723561005 774161007 781405001 1 0..* 0..1 723597001 723596005 < b1bfe4c7-b443-45fa-9653-108093235e5a 20190731 1 900000000000012004 723561005 774160008 781405001 1 1..* 1..1 723597001 723596005 < f3a97490-6c74-404e-a3e9-436b7d4ca2a1 20190731 1 900000000000012004 723561005 774159003 781405001 0 0..1 0..0 723597001 723596005 < be279b7b-2331-496c-b3e6-51b94df106fc 20190731 1 900000000000012004 723561005 774163005 781405001 1 0..* 0..1 723597001 723596005 > 391f932e-3158-47bb-a95e-a2b1c19e864d 20190731 1 900000000000012004 723561005 774158006 781405001 0 0..1 0..0 723597001 723596005 Plus 1 additional new record: > 07805dc4-f785-48f1-a7b0-b089b29f1c4e 20190731 1 900000000000012004 723561005 784276002 781405001 0 1..1 0..0 723597001 723596005d | |
| MRCM AttributeRange files | 6 | 2 records inactivated, plus 0 updated, plus 2 new records added, ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) + 5 records had the DomainID changed, as expected in ISRS-564 + "OR Medicinal product package (product)" clause removed from all records to correct erroneous Beta Version 1: < 2affaf44-9365-4d6d-84d3-31409206a77a 20190131 1 900000000000012004 723562003 774158006 << 774167006 | Product name (product name)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774158006 |Has product name| = << 774167006 | Product name (product name)| 723597001 723596005 < 355c9063-7238-4409-81a8-13f22b2a8bff 20190131 1 900000000000012004 723562003 774161007 < 260299005 |Number (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774161007 |Has pack size| = < 260299005 |Number (qualifier value)| } 723597001 723596005 < 608ab6f5-6830-4294-926a-5c3a20b62060 20190131 1 900000000000012004 723562003 774159003 << 774164004 | Supplier (supplier)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..1] 774159003 |Has supplier| = << 774164004 | Supplier (supplier)| 723597001 723596005 < e491647d-1793-4b20-b92d-c1180a96b00f 20190131 1 900000000000012004 723562003 774163005 << 767524001 |Unit of measure (qualifier value)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774163005 |Has pack size unit| = << 767524001 |Unit of measure (qualifier value)| } 723597001 723596005 < e5945adf-c075-4fb7-8f1b-515a124326cf 20190131 1 900000000000012004 723562003 774160008 << 763158003 |Medicinal product (product)| << 373873005 |Pharmaceutical / biologic product (product)|: [0..*] { [0..1] 774160008 |Contains clinical drug| = << 763158003 |Medicinal product (product)| } 723597001 723596005 SLightly different to published Internaitonal, so need to run a comparison between this optional package and the International published release to ensure the MRCM attribute Range files match... | |
| MRCM Domain files | 11 | 9 records updated, plus 1 inactivated, plus 1 new record added ?????????? as confirmed by Linda's in line with the changes she made to master sheet for the July 2019 cycle: ??????? (plus confirmed by Maria to be as expected in her email at ??????????) Same as International published release | |
| Association Reference files | 6892 | 521 records updated, plus 1687 records inactivated, plus 4741 records added Yong confirmed that this is approximately the expected amount on There are 126 new additions and 24 inactivation for the 734138000|Anatomy structure and entire association reference set (foundation metadata concept)| Slightly different to International Published release, but only by a few records so looks good | |
| Attribute Value files | 16375 | 1396 records updated, plus 176 records inactivated, 14979 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on Slightly different to International Published release, but only by a few records so looks good | |
| Language refset files | 39699 | 1004 records updated, plus 8819 records inactivated, plus 30880 records added because of a large number of description changes in product and disease hierarchies. (no data on this from qa.snomed.org) - Yong confirmed that this is approximately the expected amount on . Slightly different to International Published release, but only by a few records so looks good |