110210 care com presentation for poland v2


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

110210 care com presentation for poland v2

  1. 1. What CareComcan do by CEO Jacob Boye Hansen &Project Manager Annika Sonne Hansen<br />
  2. 2. Overview<br />Syntactic and Semantic Interoperability –Example (Alexander Graham Bell)<br />HealthTerm product<br />The epSOS project<br />Advantages<br />Security<br />Quality<br />Cost Savings<br />
  3. 3. Syntactic but not Semantic Interoperability<br />ラドクリフ、マラソン五輪代表に1万m出場にも含み<br />Bonjour mademoiselle. <br />Ça va bien?<br />
  4. 4. Syntactic AND Semantic Interoperability<br />Jes thnak vi, kaj kiel vi fartas? <br />Bonan matenon maltrafas, vin estas bone? <br />One common language is necessary – here it is Esperanto<br />
  5. 5. How do your terminologies & classifications work today?<br />SNOMED CT®<br />Export<br />SNOMED CT ® <br />server<br />HealthCare system<br />HealthCare system<br />Web interface<br />ICD-10<br />ICD-10<br />server<br />Export<br />HealthCare<br />system<br />Web interface<br />ICF<br />ICF<br />server<br />Export<br />Web interface<br />Other classifications<br />Other classification<br />servers<br />HealthCare<br />system<br />Export<br />X numbers of <br />terminologies and <br />classifications<br />X numbers of <br />servers, database licences <br />& software applications<br />X numbers of <br />exports & <br />web interfaces<br />X numbers of <br />HealthCare systems<br />
  6. 6. How should your terminologies & classifications work:<br />SNOMED CT®<br />HealthTerm®<br />terminology<br />&<br />classification<br />server<br />HealthCare system<br />HealthCare system<br />ICD-10<br />HealthCare<br />system<br />Web interface<br />ICF<br />Other classifications<br />HealthCare<br />system<br />X numbers of <br />terminologies and <br />classifications<br />1 server, 1 database licence <br />& 1 software application<br />1 web interface<br />X numbers of <br />HealthCare systems<br />
  7. 7. What is HealthTerm about:<br />One repository for all terminologies and classifications. A one-stop ontology service<br />Web application with:<br />Concept Browser<br />Request & Editing module <br />Mapping module<br />Subset module<br />Qualification module<br />Translation module<br />Distribution module<br />Workflow mechanism<br />History mechanism<br />
  8. 8. Web application:<br />User controlled access through the internet<br />No local installation<br />All data in real time<br />No data exchange<br />
  9. 9. Concept Browser:<br />Access to different terminologies and classifications is controlled by user setup<br />
  10. 10. Concept Browser:<br />Show all terminologies and classifications in the same browser window<br />Concepts and terms shown in their context.<br />
  11. 11. Concept Browser:<br />Display of user interface and content is based on language setup<br />Local language of terminologies & classifications requires translation<br />
  12. 12. Request & Editing:<br />Maintenance of terminologies and classifications<br />Suggest new or missing concepts and terms in the request module<br />User controlled access<br />
  13. 13. Request & Editing:<br />Create new concepts or terms<br />Edit existing concepts<br />Edit or create descriptions<br />Edit or create relations<br />Edit existing terms<br />Edit or create properties<br />Validate<br />Publish <br />
  14. 14. Request & Editing:<br />Since it is a web application new or edited concepts and terms will be available for all other users the same second they have been published<br />No data exchange<br />All terminologies and classifications can be maintained on the same database with the same application<br />User controlled access<br />
  15. 15. Mapping: <br />Mapping between different terminologies & classifications<br />Mapping between clinical and accounting classifications can prevent double entries and ensure more correct financial settlements<br />
  16. 16. Mapping: <br />Mapping between local and international classifications for exchange of clinical & statistical data<br />Quick map feature<br />Workflow mechanism to ensure quality<br />
  17. 17. Subset:<br />Create subsets in order to get a manageable amount of concepts or terms to work with:<br />Subsets for editing <br />Subsets for mapping<br />Subsets for qualification<br />Subsets for translation<br />Clinical subsets for distribution purposes<br />Workflow mechanism to ensure quality<br />
  18. 18. Qualification:<br />Qualification to validate clinical use of concepts and terms<br />Qualification to add synonyms, clinical dialects and layman’s language<br />This can be done at different levels, and allows distribution of clinical subsets for use in different contexts to ensure semantic interoperability<br />Workflow mechanism to ensure quality<br />
  19. 19. Translation:<br />Translate to local language based on the context <br />Get help from previous translations in same translation project or other translation project<br />Apply term references or web links that supports the translation<br />Workflow mechanism to ensure quality<br />
  20. 20. Translation:<br />Monitor progress<br />
  21. 21. Distribution:<br />Distribute at realm or context level:<br />Full export<br />Delta export<br />Custom Export<br />Distribute different formats<br />
  22. 22. Workflow mechanisms:<br />Different workflows in different modules<br />Ensuring quality in data enrichment<br />Subset Selection<br />Translation Service Provider<br />Batch creation<br />(Concept Manager)<br />Translation<br />Translation <br />Review<br />Subject Matter <br />Expert<br />Editorial Board<br />Internal Review<br />Concept <br />Published<br />
  23. 23. History mechanisms:<br />History for the different workflow steps<br />History for terminologies and classifications<br />
  24. 24. Data at different levels:<br />All data can be shown and maintained at different levels in order to cope with different use of data at different levels:<br />International level<br />National level<br />Regional level<br />Local level<br />Specialist level<br />General level<br />Public level<br />
  25. 25. Perspective:<br />Subject Matter Expert<br />Translation Service Provider<br />IT Suppliers EHR<br />IHTSDO<br />National Authorities<br />WHO-FIC<br />Local Authorities<br />CCI/OQLF<br />Regional Authorities<br />Hospital<br />General Practitioner<br />Community<br />Care<br />
  26. 26. The maintenance covers e.g. the translation and transcoding (mapping) process where each MS translates to local language and transcodes from local classification(s) to epSOSclasifications<br />Page 26<br />Terminology maintenance<br />Valueset<br />selection<br />Service Provider<br />Batch creation<br />(Concept Manager)<br />Translation /<br />transcoding<br />Review<br />Subject Matter <br />Expert<br />Maintenance workflow<br />Subsets<br />Terminology Repository<br />Editorial Board<br />Internal Review<br />Central codingsystems<br />Local codingsystems<br />Published<br />
  27. 27. Terminology Maintenance Tool<br />Subject Matter Expert<br />Translation Service Provider<br />IT Suppliers <br />WHO<br />(ATC)<br />National Authorities<br />WHO<br />(ICD 10)<br />LOINC<br />Mapping<br />expert<br />Classification Centre #1<br />Classification Centre #2<br />Classification Centre #3<br />
  28. 28. Advantages - Security<br />One system only for the maintenance and exchange of terminology and classificationrelated information<br />One user interface allowsaccess to ALL terminologies and classifications<br />All feeder systems arealways up-to-date, as they all make the look-ups oneplace. This prevents a feedr system to be ”forgotten”<br /><ul><li>All clinical IT systems collect information from one source, whichmeansthattheysharethe SAME information = onecommonlanguage = semanticinteroperability
  29. 29. Patient safety in as much as admissions, orders, prescriptions, reports etc. Alwaysreachtheir destination and is understoodcorrectly, as there is semanticinteroperability</li></li></ul><li>Advantages - Quality<br />Havingonlyoneaccessroad to ALL terminologies and classificationsensures a higherquality of the data beingentered<br />Web Services betweenclinical systems exchangingcodified data ensuresalways up-to-date data<br />ALL systems useoneterminology service This meansimprovedconsistency<br />Impossible for the same code to have differentmeanings in different systems – or twocodeshaving the same meaning<br />Significantimprovement in producingstatistics<br />Errorcorrections and manual updatesareminimised<br />Medicine lists areidentical at all hospitals. Central management<br />Missing or differentlocal organisation codesno longer createdelays or faulty patient treatments<br />
  30. 30. Advantages – CostSavings<br />All classifications are maintained and further developed in ONE place only<br />Many external consultancy hours may be saved by having ONE system only that does much of the work for you<br />You can save on hardware and software, as thefunctionality is in ONE place only<br />Internal time savings by keeping data up-to-date in ONE place only<br />Error corrections and manual updates are minimised<br />No longer any reason to keep track of several copies of (almost) identical classifications. Previously this work had to be repeated for every new system to be integrated<br />Medicine lists are identical at all hospitals. Centrally managed, which drugs are used/recommended (price/quality)<br />
  31. 31. Classification broker<br />PAS<br />EMR<br />Labsys<br />Patho-logy<br />Ambu-lance<br />Micro-biology<br />Clinical and administrative staff can access HT directly through the user interface<br />All administrative and clinical systems retrieves codified information from one place only<br />Health-Term®<br />All terminologies, classifications and local code books are maintained one place only<br />All hospitals draw upon the same service<br />Regional org. classif., ICD-10, SNOMED CT, IUPAC, ATC, local code books, etc. etc. <br />