1 / 13

Content Development – where we are, and where we want to be

Content Development – where we are, and where we want to be. Ian Green Content Development Manager. Authoring capacity. Internal team √ Chief Terminologist 6 x authors Consultant Terminologists √

lavina
Download Presentation

Content Development – where we are, and where we want to be

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Content Development – where we are, and where we want to be Ian Green Content Development Manager

  2. Authoring capacity • Internal team √ • Chief Terminologist • 6 x authors • Consultant Terminologists √ • 9 x certified (Case, Cheetham,Fung, Goldberg, Muys, Reynoso, Richardson, Rogers, Wade) • 4 x working on certification • External contractors √ • 3 x external contractors currently (or soon to be) engaged in authoring activities (2 of whom – Reynoso, Wade – are also Consultant Terminologists) “Never was so much owed by so many to so few”

  3. Current issues – across all strategic programs • Managing (clearing) the request submission backlog • Use of more liberalapproach (unmodelled leaf node additions) - 4,800 total outstanding requests, aim to author 3,800 • Managing and resolving issues in the content tracker • 671 Tracker items • Inception – 461 • Elaboration – 154 • Construction – 42 • Transition – 14 300 man years – 80% with 20% effort (60 man years) • Management, resolution and implementation of precoordination roadmap • 200 tracker items • Managing internally generated requests from SIGs • Should clinical requests from SIG’s take priority?

  4. Issues going forwards • Horizontal modelling • Use of batch template-based editing • Tooling requirement • Review process • Increasing levels of authoring/content review • Expansion of capacity to deliver content review • Distributed asynchronous authoring • Further development of current ways of working • Tooling support for authoring activity within and outside the organisation

  5. Growing the authoring community • Assumptions • Internal authoring resource will not deliver enough capacity • We need to maximise the authoring capacity we have access to • Consultant Terminologists will continue to assist in the process • Where possible we will continue to use external contractors • Current status - demand outstrips delivery • Increasing levels of request submissions • Large numbers of complex content issues to address • Increasing number of competing priorities

  6. Where will capacity come from ? • Internal team • Planned increase in the internal authoring team (10 authors) • Improved tooling (ability to edit bulk changes) • IHTSDO community of practice • Consultant Terminologist Programme (CPT) • Regular author training sessions (open to all) • Bespoke training sessions provided on request • Maximising the use of CPT’s in national release centres • Clinical expertise • Engagement of clinical groups on specific topic areas • Tooling enhancements

  7. Content Development – Strategic overview Kent Spackman Chief Terminologist

  8. - alpha Roadmap for Content Development (rev 8/13) -preview Problem List - release Anatomy Problem list use case Allergens Allergies Allergen Substances Allergy use case Drugs Meds Medication Substances Drug product use cases Orders Results LOINC Lab Observations Clinical Observations test Reportable Diseases Organisms model Public Health Reporting Devices GMDN technology preview Integration of GMDN device content with SCT Interventions & Plans Interventions Continuity of care – discharge plans Conditions Situations Condition/situation (and ECE) solution ICD11 foundation layer – linkage & integration Ju 13 Ju 14 Ja 13 Jan 14 Jan 15 Oct 13 July 13 July 14 July 15 Ju 12

  9. ICD-11 Common Ontology Work (#8 in roadmap) • Seeking to align SNOMED CT and ICD-11 development • Initial topic area: circulatory diseases • Has identified significant gaps in SNOMED CT content • Relative to the expanded draft ICD-11 content, as developed by WHO Topic Advisory Groups • Example: pulmonary hypertension

  10. Example: Pulmonary hypertension Prompted by query from US FDA for drug indication coding (we had the concept but it was poorly labeled) Before revision: 36 concepts After revision: 57 concepts, (reorganized, restructured)

  11. ICD-11 beta (2012) - number of concepts by chapter

  12. Implications for content authoring • Need to identify gaps across all 22 disease chapters • Independent input from clinical groups (slow, hit-or-miss) • Proactive identification via • Comparison with ICD-11 draft • Literature searches for verification • Requests to IHTSDO NRCs for surveillance of user needs? • Need to develop consensus views of changes needed to SNOMED CT • Conversations with ICD-11 Common Ontology Working Group • Queries via WHO team to WHO Topic Advisory Groups • Need to update content in identified gap areas • Effort required: see next slide

  13. (8) ICD-11 linkage and integration Rough estimate of amount of effort required: Extrapolated Actual Sept 2012 9,523 concepts / 20 concepts per day = 476 days of effort (~22 mythical man-months)

More Related