More Related Content More from semanticsconference (20) 1. 1
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Registry of clinical data for
PSSO
Krzysztof Cieśliński
Solution Architect
Rectal cancer module
2. 2
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Who we are : Cognitum
Fluent Editor
Ontorion Server
Ask Data Anything (ADA)
Ontorion
Controlled
Natural
Language
3. 3
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Introduction
4. 4
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
What ?
Central registry for collecting patient’s clinical data from over 70
oncological institutions in Poland. In production since 2016.
Who ?
Polish Society of Surgical Oncology(PSSO)
Why ?
Find out in which group of patients stoma surgery should be applied
(in this particular module).
5. 5
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
How ?
6. 6
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Project requirements
Expandable – new modules for future clinical examinations
Easy to maintain
Secure – sensitive patients data
Scalable
Intuitive
7. 7
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Automatic Reasoning Based
User Interface
8. 8
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
From knowledge in natural language..
OWL/RDF compatible
9. 9
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
10. 10
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
General idea
Domain
knowledge
UI
knowledge
UI
Generated
knowledge
11. 11
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Form structure
Form
Section
Field
Dynamic Field
All labels/texts are
OWL Annotations
12. 12
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Basic type fields
Every personal-information-section must have-social-security-number (some string value).
have-social-security-number rdfs:label PESEL @PL
Annotations:
have-social-security-number arbui:validation '^d{11}$'
13. 13
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Single choice fields
Every personal-information-section must have-sex a sex.
Something is a sex if-and-only-if-it is either Male or Female.
have-sex rdfs:label Płeć @PL
Annotations:
Male rdfs:label Mężczyzna @PL
Female rdfs:label Kobieta @PL
14. 14
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Multiple choice fields
Every studies-data-section must have-interview-data a interview-data.
Something is a interview-data if-and-only-if-it is either … or … .
Annotations:
have-interview-data arbui:render-opts 'checkboxlist'
…
15. 15
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Dynamic fields - reasoning
16. 16
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
General Architecture
AJAX
17. 17
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Maintenance
– real life example
18. 18
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Maintenance - Problem
Change in one of the forms:
As field X depends on answer to the field Y, it should
be moved to the dynamic section Z, which is triggered
by answer to field Y.
5 months after application deploy
19. 19
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Maintenance - Solution
Modify database knowledge using OntorionCMD tool:
Remove:
Every post-operation-module-psso-01 must
have-anastomosis-leak-occurrence-time (some integer value).
Add:
Every extended-post-operation-module-psso-01 must
have-anastomosis-leak-occurrence-time (some integer value).
20. 20
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Live demonstration
21. 21
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
ARBUI – characteristics summary
OCNL support
Expandability
Requirements traceability
Ease of internationalization
Real time reasoning
Ease of application maintenance
Domain independent
22. 22
The company, product and service names used in this web site are for identification purposes only.
© Cognitum 2014. All trademarks and registered trademarks are the property of their respective owners.
Thank you!
Krzysztof Cieśliński
Solution Architect
k.cieslinski@cognitum.eu
Cognitum Sp. z o.o.
Ząbkowska 27/31, Warsaw, Poland
http://www.cognitum.eu/, office@cognitum.eu
Windows Azure Circle Partner
MEMBER
Editor's Notes Good Morning everybody, my name is Krzysztof Cieśliński. I’m solution architect in Cognitum company and I’m going to present one of our projects which utilizes semantic technologies. Maybe some of you know the Fluent Editor – ontology editor
Ontorion server – Distributed Knowledge Management System with Natural Language interface
ADA – business intelligence tool
Few basic questions at the begining.
The registry entry point is a web application with forms which are filled by doctors.
Who ordered.
Why – PSSO has started a new clinical examination and they wanted to have a central registry for collecting clinical data about it
First and the most important requirement for PSSO is that appllication can be easily expanded with new modules, for new clinical examinations. So right now we have single module – the rectal cancer but in future there will be more.
Easy to maintain – the clinical examination protocols are pretty complex and it can happen that during implementation some bugs can appear, or for the analysis purposes doctors can store more data
Secure – There are 70+ institutions which are treating cancer, and patient sensitive data can be viewed only by doctors from institution which is treating that particular patient.
Scalable – in many ways, number of patients/modules/doctors who are working with the application.
Intuitive – Surgeons are very busy people, and their time is really precious. So the user interface have to be really clear and intuitive. Someone said that user interface is like a joke – if you have to explain it then it’s not so good.
Meet the requirements We have knowledge which is divided to UI knowledge and Domain knowledge. First describes the schema so the forms, sections fields and relations between them, while second defines the contents of the forms – so the specific questions, answeres and transitions.
These two sets intersects and then the ARBUI mapper is able generate UI from it.
So filling up the forms generates new knowledge about the answeres which can trigger generation of other fields/sections or even whole forms. They do not differ We don’t have to show all the fields at once. Thank you for your attention!
