Revision [123]
Last edited on 2010-05-01 03:02:43 by MartinWehlouAdditions:
=====Manageable structure of data=====
A major problem with current EHR systems has recently surfaced as more and more information is pumped in. The problem is that the individual doctor becomes incapable of reviewing the information before or during a patient encounter, due to lack of summaries or correct views on data. Summaries used to help us a lot when EHR systems were not interconnected, since any EHR records that were received from other systems usually arrived on paper and had to be added to your own EHR as a concise summary. This only had to be done once. With interconnected systems, such summaries aren't made anymore, and every doctor that accesses the EHR needs to do this summary himself in his mind, only to lose it again after the encounter. This has quickly overwhelmed doctors and in practice, most patient files are now only skimmed instead of read, making the doctor's awareness of the patient's history more sketchy that ever before. iotaMed, on the other hand, introduces "issues" that present a top-down view of diseases, supplying the missing element that allows an overview of the EHR contents at a glance.
A major problem with current EHR systems has recently surfaced as more and more information is pumped in. The problem is that the individual doctor becomes incapable of reviewing the information before or during a patient encounter, due to lack of summaries or correct views on data. Summaries used to help us a lot when EHR systems were not interconnected, since any EHR records that were received from other systems usually arrived on paper and had to be added to your own EHR as a concise summary. This only had to be done once. With interconnected systems, such summaries aren't made anymore, and every doctor that accesses the EHR needs to do this summary himself in his mind, only to lose it again after the encounter. This has quickly overwhelmed doctors and in practice, most patient files are now only skimmed instead of read, making the doctor's awareness of the patient's history more sketchy that ever before. iotaMed, on the other hand, introduces "issues" that present a top-down view of diseases, supplying the missing element that allows an overview of the EHR contents at a glance.
Revision [122]
Edited on 2010-04-26 04:42:08 by MartinWehlouAdditions:
=====Database structure flexibility=====
Since iotaMed is based on a graph database, it can include a great variety of medical data structures without any data element restrictions applied at the design stage, which is the major problem with current systems that use relational databases.
=====Distributed data=====
The graph database format is based on RDF, which makes the reference to external data sources much simpler and allows inclusion of documents into a medical record irrespective of the source of those documents, greatly reducing the effort needed to interconnect different sources of records data for the patients.
Since iotaMed is based on a graph database, it can include a great variety of medical data structures without any data element restrictions applied at the design stage, which is the major problem with current systems that use relational databases.
=====Distributed data=====
The graph database format is based on RDF, which makes the reference to external data sources much simpler and allows inclusion of documents into a medical record irrespective of the source of those documents, greatly reducing the effort needed to interconnect different sources of records data for the patients.
