Product | Edition | Product Status | Release Frequency | Current Release Status | Next Scheduled Release | Next Release Status | Comments | Documentation |
---|---|---|---|---|---|---|---|---|
SNOMED CT International Edition | International | Maintenance | 6 months (January/July) | Production | 20150731 | Production | ||
SNOMED to ICD-10 Map | International | Maintenance | 6 months (January/July) | Production | 20150731 | Production | 02/04/2015 - Kathy and team just finalising data on this - Brian will export from refset tool once completed - Brian to confirm to me when we need to deploy.
Plan to receive large update to the ICD-10 content by end of March 2015 - Brian will deliver the files, and we will need to publish the candidate baseline separate to the international release (as soon as possible) - then once in production this needs to be part of the international edition.
QUESTION For Robert - IGR has suggested that all refsets and maps should not go out as Tech Previews, just as Candidate Baselines (with potentially extended deadlines), as the formats are fixed and immutable, and so we do not want any feedback on this, we just need to send them out as Candidate Baselines in order to give visibility of hte content early. This gives more context for the users, who will be more likely to look carefully at candidate baselines rather than tech previews. | |
SNOMED to ICD-10CM Map | International | Development | 6 months (January/July) | TBC | TBC | TBC | This is the US 'extension' of ICD-10, which they will be adopting around November 2015, in place of ICD-9CM (which will be targeted for deprecation shortly afterwards) | |
SNOMED to ICD-10PCS Map | International | Development | 6 months (January/July) | TBC | TBC | TBC | This map is being developed in conjunction with several european countries, but is a completely different structure to ICD-10 and ICD-10CM, so in 2016 we need to discuss with IGR how we will incorporate this | |
SNOMED to ICD-9CM Map | International | Maintenance | 6 months (January/July) | Production | 20150731 | To be Deprecated | Targeted for Deprecation by 31/07/2016. Link to proposed Deprecation document: Deprecation_SNOMED CT to ICD-9-CM Epidemiological and Statistical Map v0.03.docx | |
SNOMED CT to ICD-O Map | International | Maintenance | 6 months (January/July) | Production | 20150731 | Production | 1. Would IGR be able to explain to Yong how to maintain this in the Workbench? - Yes we can, Yong currently maintains it but in a separate DB, 2016 onwards maintenance will move from Yong to mapping team. Plan is to move DB into the Terminology server - IGR to discuss timeline with RTU due to potential risks with doing this simultaneously with Terminology Server upgrade. | |
SNOMED Identifier Subset (RT) | International | Maintenance | 6 months (January/July) | Production | 20150731 | To be Deprecated | Link to press release regarding deprecation timeline: | |
CTV3 Identifier subset | International | Maintenance | 6 months (January/July) | Production | 20150731 | To be Deprecated | 3. Link to Deprecation notice: http://www.hscic.gov.uk/media/15868/1553disn/pdf/1553disn.pdf The UKTC aims to withdraw the Read Codes form use as of April 1st 2020. IHTSDO should aim to withdraw the CTV3 identifier reference set as of the January 2020 release. | |
SNOMED to ICPC2 Map | Derivative | Development | TBD; To be released 6-8 weeks after the International edition. | Candidate Baseline | 20150930 | Candidate Baseline | ||
SNOMED to GP/FP subsets | Derivative | Development | TBD; To be released 6-8 weeks after the International edition. | Candidate Baseline | 20150930 | Candidate Baseline | 02/04/2015 - Per IGR, the refsets need to be consolidated into a single refset under the ID: 450970008 |General Practice / Family Practice reference set (foundation metadata concept)| AA to ask RTU whether or not we can do some additional work to the refset tool in order to do this in a controlled manner, or if we should just do it manually (IGR can pass us the changes to the content, and we can get the 2 separate refset files from collabnet) IGR happy for us to action after Spanish Release is sorted out, as not imminently urgent - basically we need to amalgamate the 2 refsets for him before he updates the content, as otherwise they will have to update it in 2 places (both separate refsets) and then amalgamate, creating redundant workload. | |
SNOMED CT Spanish Edition | Spanish | Maintenance | 6 months (April/October) | Production | 20150430 | Production | 02/04/2015 - Termmed confirmed 3000 concepts may be problematic to translate in time, due to nuances in language and badly defined GMDN concepts. AA to confirm with RTU if standard practice is to push them into next release. Schedule cannot change as can't translate the Spanish Release until International Release has been published. | |
SNOMED CT Estonian Release | Estonia | Development | 6 months (April/October) | Alpha | TBC | Production | IHTSDO will assist Estonia in the creation of their first release, with the agreement that they will expect no long term support from IHTSDO, as they will quickly learn how to create their own extension (hence why this is a Release and not an "Edition"). The first release will include their refsets. | |
Kaiser Permanente (CMT) Starter Reference Sets | Derivative | Development | As and when updates are available (as not published through Release Management) | Technology Preview | TBC | Candidate Baseline | 02/04/2015 - Expecting next update from KP in Q3 2015 - so next release will be subsequent to this.
We publish the refsets as spreadsheets on the Member forum, and anything deemed worthy of inclusion in the International edition is then incorporated accordingly. Anything USA-specific is passed to the NLM for inclusion in the USA release. | |
Kaiser Permanente subset of the top 2500 codes used in KP (NLM CORE subset) | International | Development | 6 months (January/July) | Production | 20150731 | Production | 5. Need to find out... is the KP subset the same as the NLM CORE subset ( which IHTSDO published once as 700043003 |Example problem list concepts reference set (foundation metadata concept)|) , and is the content from the subset modeled in SNOMED as it is updated by either or both of KP and NLM? - IGR confirmed that there are 2 x top 2500 subsets, one for KP and one for NLM CORE - technically 2 separate products, which are published (on the member exchange in collabnet), but only the NLM CORE subset is used in the international edition, as the KP subset contains laterality data which we currently can't support in the International edition.
These are currently incorporated into the International edition as as part of the IHTSDO content authoring process. | |
SNOMED to LOINC map | Derivative | Development | 6 months (January/July) | Technology Preview | 20150731 | Candidate Baseline | Final Tech Preview due out in July 2015. Targeted for Production Release in January 2016. | |
SNOMED to ICN map (Nursing) | Derivative | Development | 6 months (January/July) | Technology Preview | TBC | Candidate Baseline | 02/04/2015 - AA to talk to RTU about Release capacity, as this needs to be released by end of April (or very shortly afterwards), as it's currently based on January 2015 release - any later than this and it might as well be related to July release instead and we'll have missed our window. 6. To follow up with IGR - Now have a date, looking at linkage table being delivered to us by 13/04/2015 (nursing diagnosis), and another linkage table (nursing interventions) delivered to us Q3 2015. So first one we can release the candiadte baseline in May 2015, get feedback and ask ICN to update, with intention of production release in Q3 2015.
| |
SNOMED to ICD11 map (WHO) | TBC | TBC | TBC | TBC | TBC | TBC | 02/04/2015 - AA to talk to RTU about Release capacity, as we need to let them know if we won't be able to get the 350 initial concepts into the July 2015 release due to bandwidth issues Currently in an SQL DB until the WHO decide what to do with Linearizations - therefore presently out of scope of the content authoring process. | |
Medical Devices | International | Maintenance | 6 months (January/July) | Production | 20150731 | Production | 02/04/2015 - ***** We need to provide Termmed with visibility of any new data that comes through as early as possible, in order that they can begin translation into Spanish asap, to ensure it all gets completed by October 2015 release. Per agreement with NJA and IGR, no new content until preparatory work has been completed. Scope of this work to be determined. Robert to discuss with IGR once evaluation of quality of new GMDN data has been completed - we can then decide what needs to be done in order to prepare it for the July 2015 release. | |
ADA Dentistry findings | International | TBC | 6 months (January/July) | TBC | TBC | TBC | Currently haven't agreed with the ADA exactly what we're publishing - therefore presently out of scope of the content authoring process. | |
Anatomy content | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | University of Washington won't be finished with it until July 2015 at least, so targeted for Production Release in January 2016 at the earliest. | |
HIV Refset | Derivative | Development | 6 months (January/July) | Technology Preview | TBC | Technology Preview | RTU updated set of concepts from Ronald Cornet, and sent them back to him on 02/03/2015. AA chased Anna (to see if Ronald had reviewed them) on 19/03/2015 - Anna confirmed on 07/04/2015 that Ronald is now on holiday, and so won't be able to respond to us now before end of April - Anna wanred them that this will impact our timelines - she will send us the files once Ronald has returned and sent them to us. | |
Pharmaceutical model | ||||||||
| International | Maintenance | 6 months (January/July) | Production | 20150731 | To be Deprecated | IGR agreed with Nilesh that we create them for July 2015, but not include them in the Release - just put out comms to say they're available on request. If no-one using them we can deprecate, if people are using them we need to update them in line with the DMND product content. | |
| International | Maintenance | 6 months (January/July) | Production | 20150731 | To be Deprecated | IGR agreed with Nilesh that we create them for July 2015, but not include them in the Release - just put out comms to say they're available on request. If no-one using them we can deprecate, if people are using them we need to update them in line with the DMND product content. | |
| International | Development | 6 months (January/July) | Technology Preview | 20150430 | Candidate Baseline | 02/04/2015 - Brian still working on this - need to check on progress Toni/Romin just finishing this off - due to come to us approx start of April - with requirement to be published around end of April AA/RTU to sort out access DB to RF2 format conversion via Brian - Meeting with everyone to discuss next steps set for | |
| International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | Targeted for Production Release in January 2016. | |
| International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | 02/04/2015 - Proposed model was rejected by focus group, so IGR taking new proposed model to Copenhagen conference for approval - definitely won't get into July 2015 release now Targeted for Production Release in January 2016. | |
| International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | Targeted for Production Release in January 2016. | |
Observables model | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | Targeted for Production Release in January 2017. | |
Microbiology subset | International | Development | 6 months (January/July) | Alpha | TBC | Production | 02/04/2015 - IGR made changes to release content now, they need to create a subset of values for that - IGR to chase Farzaneh and come back to me with update - we will target a Candidate Baseline alongside the July 2015 release. 7. To follow up with IGR... "No Tech Preview required - this will be incorporated, as refsets, directly into the International edition via the content authoring process." - Should go out as a candidate baseline (as format is immutable) - yet we still reserver the right to change the format/content if we like befor the production release. Targeted for Production Release in July 2015. | |
Functioning model | International | Development | 6 months (January/July) | Technology Preview | 20150731 | Candidate Baseline | Targeted for Production Release in January 2016. | |
Situations model | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | Targeted for Production Release in January 2017. | |
GINAS | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | Not yet confirmed as to exactly what will be included - just placeholder for now. | |
ORPHANET in SNOMED CT | International | Development | 6 months (January/July) | Candidate Baseline | TBC | Production | 02/04/2015 - AA to speak to RTU regarding capacity, as we need to confirm to Jane by 08/04/2015 as to whether or not Brian can get them the Orphanet data by mid April still??? Orphanet (Rare Diseases) content targeted for Production Release in January 2016. Tech Preview/Candidate Baseline to be scheduled once everything received from INSERM. | |
Nutrition/Dietetics | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | This is purely content, and so will have no Release deliverables distinct from the International content. | |
Procedures | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | This is purely content, and so will have no Release deliverables distinct from the International content. | |
Oncology | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | This is purely content, and so will have no Release deliverables distinct from the International content. | |
Genomics | International | Development | 6 months (January/July) | Alpha | TBC | Technology Preview | This is purely content, and so will have no Release deliverables distinct from the International content. |