The an open source browser will be great for researchers and
academics. Subsetting may be particularly important, as some people
think that accurate coding of an appropriate subset is critical for
decision support functionality...but is yet to be demonstrated and
verified by research. If this is true, then being able to demonstrate
robustness and maintainability of subsets is important.
Grassroots clinicians will get more use out of your text processing
system so they can easily record whatever notes they need to but get
close to correct codes in the right fields in their clinical system.
To make this work, integration into clinical systems through a
"presently nonexistent" standard interface is needed.
Perhaps its worth looking at the architecture of the GPCG
Interoperability Project (and subprojects) run by David Rowed, which
was designed to deliver clinical system components and thin
interfaces. Horst had significant input into it.
Browsing for clinicians will be used primarily when doing searches.
Integration of browsing functionality with existing clinical system
database search functions would be good. How this will work with a
web interface I'll leave to you....
Ian.
At 8:13 am +1000 18/7/06, [EMAIL PROTECTED] wrote:
Dear List, below is a text describing a project I intend offering to my
students for the coming semester. I would be grateful if you could make
any additions or comments to enhance the specification. Acknowledgements
to Tim Churches for his contribution to the text.
thanks
Jon
Web Interface for Maintaining Medical Ontology, SNOMED CT
Introduction
With the adoption of the ontology SNOMED CT (SCT) by the Australian
Government for reporting clinical content a brand new sub-market in
SNOMED-CT-related health IT software has opened up overnight in Australia.
The aim of this project is to provide an open source system to support its
adoption.
Aim
To build a Web-based SNOMED-CT browser/search facility, perhaps using some
nifty Web 2.0/AJAX methods to provide good interactivity. At the moment,
most SNOMED-CT browsing is done using a free (but not open source) Visual
Basic GUI application called CLUE (see
http://www.clininfo.co.uk/clue5/index.htm ). A SNOMED-CT look-up facility
as a Web service licensed under an open source license which permitted
integration with both open source and closed source clinical applications
(i.e. Mozilla, BSD licenced) is needed.
The system should also provide for a number of other functions needed to
maintain it and support particular users, such as:
Specialist subsetting
Subsumption testing over all transitive relationships
Inheritance mapping
Hierarchy visualisation
Minimum Network presentation
Integration with the current Text-to-SCT processing system
Comparison to other Systems
The problem with the CLUE browser, apart from its general clunkiness and
not terribly smart look-up facilities, is that it needs to be installed,
along with the SCT data files, everywhere you need to use it.
Another product MyCroft that maintains SNOMED CT is produced by Apelon
TermWorks and may give further ideas on utilities see
http://www.apelon.com/ .
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
--
Dr Ian R Cheong, BMedSc, FRACGP, GradDipCompSc, MBA(Exec)
Health Informatics Consultant, Brisbane, Australia
Internet: [EMAIL PROTECTED]
(for urgent matters, please send a copy to my practice email as well:
[EMAIL PROTECTED])
PRIVACY NOTE
I am happy for others to forward on email sent by me to public email lists.
Please ask my permission first if you wish to forward private email
to other parties.
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
