gnumed-doc 1.4.6+dfsg-1 / usr / share / doc / gnumed / user-manual / Gnumed / PaperToEmr.html

This file is indexed.

/usr/share/doc/gnumed/user-manual/Gnumed/PaperToEmr.html is in gnumed-doc 1.4.6+dfsg-1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below. 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en_US" lang="en_US">
<head>
	<title> PaperToEmr &lt; Gnumed &lt; Foswiki</title>
		  
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta name="robots" content="noindex" /> <link rel="alternate" type="application/rss+xml" title="RSS Feed" href="WebRss.html" />
	<link rel="icon" href="../rsrc/System/ProjectLogos/favicon.ico" type="image/x-icon" /> <link rel="shortcut icon" href="../rsrc/System/ProjectLogos/favicon.ico" type="image/x-icon" />
	<link rel="alternate" href="http://wiki.gnumed.de/bin/edit/Gnumed/PaperToEmr?t=1391005515" type="application/x-wiki" title="edit PaperToEmr" />
	<meta name="description" content="PaperToEmr" />
	 <!--[if IE]></base><![endif]-->
	
	<style type="text/css" media="all">
@import url('../rsrc/System/SkinTemplates/base.css');
</style>
<style type="text/css" media="all">
@import url('../rsrc/System/SkinTemplates/default.css');
</style>
<!--[if IE]><style type="text/css" media="screen">
pre {
	overflow-x:auto;
	padding-bottom:expression(this.scrollWidth > this.offsetWidth ? 16 : 0);
}
</style>
<![endif]-->

<meta name="foswiki.PUBURL" content="http://wiki.gnumed.de/pub" /> <!-- PUBURL -->
<meta name="foswiki.PUBURLPATH" content="/pub" /> <!-- PUBURLPATH -->
<meta name="foswiki.SCRIPTSUFFIX" content="" /> <!-- SCRIPTSUFFIX -->
<meta name="foswiki.SCRIPTURL" content="http://wiki.gnumed.de/bin" /> <!-- SCRIPTURL -->
<meta name="foswiki.SCRIPTURLPATH" content="/bin" /> <!-- SCRIPTURLPATH -->
<meta name="foswiki.SERVERTIME" content="29%20Jan%202014%20-%2015:25" /> <!-- SERVERTIME -->
<meta name="foswiki.SKIN" content="twikinet%2c%20pattern" /> <!-- SKIN -->
<meta name="foswiki.SYSTEMWEB" content="System" /> <!-- SYSTEMWEB -->
<meta name="foswiki.TOPIC" content="PaperToEmr" /> <!-- TOPIC -->
<meta name="foswiki.USERNAME" content="KarstenHilbert" /> <!-- USERNAME -->
<meta name="foswiki.USERSWEB" content="Main" /> <!-- USERSWEB -->
<meta name="foswiki.WEB" content="Gnumed" /> <!-- WEB -->
<meta name="foswiki.WIKINAME" content="KarstenHilbert" /> <!-- WIKINAME -->
<meta name="foswiki.WIKIUSERNAME" content="Main.KarstenHilbert" /> <!-- WIKIUSERNAME -->
<meta name="foswiki.NAMEFILTER" content="%5b%5cs%5c*%3f~%5e%5c%24%40%25%60%22'%26%3b%7c%3c%3e%5c%5b%5c%5d%23%5cx00-%5cx1f%5d" /> <!-- NAMEFILTER --><!--JQUERYPLUGIN::FOSWIKI::META-->
<script type='text/javascript' src='../rsrc/System/JQueryPlugin/jquery-1.4.3.js'></script><!--JQUERYPLUGIN-->
<script type='text/javascript' src='../rsrc/System/JQueryPlugin/plugins/livequery/jquery.livequery.js'></script><!--JQUERYPLUGIN::LIVEQUERY-->
<script type='text/javascript' src='../rsrc/System/JQueryPlugin/plugins/foswiki/jquery.foswiki.js'></script><!--JQUERYPLUGIN::FOSWIKI-->
<script type='text/javascript' src='../rsrc/System/JSTreeContrib/jquery.jstree.js'></script><!--JQUERYPLUGIN::JSTREE-->
</head>
<body class=""><div class="foswikiPage">
<a name="PageTop"></a> 
<p></p>
<p></p>
<h1><a name="Paper_to_EMR_Transition"></a>  Paper to EMR Transition </h1>
<p></p>
<h2><a name="Step_1:_Populate_an_electronic_index_of_patients"></a>  Step 1: Populate an electronic index of patients </h2>
<p></p>
Most doctors possess some kind of electronic index of their patients, commonly from billing or scheduling systems, and from which they will try to at least "seed" their EMR with a list of patients to whom care had been provided. Minimum "ported" information may be the patients' names, dates of birth, sex (gender), possibly their health insurance number(s), and possibly additional names (aliases) if these were supported in the source system. Possibly the dates of first service and last service (but note GNUmed does not at the present time hold any appointment information.)
<p></p>
The above depends on being able to get this information out of the old system, without having to pay ridiculous charges, and getting it in a form that will go into the new EMR.
<p></p>
One option by which to transfer and import the data would be in a "batch" mode. Th alternative would be on an as-needed basis if where single patients' data can, on demand, be exported from its origin and then imported into GNUmed. It is possible to define for GNUmed an importer template to understand the form and content of the external data. GNUmed also offers a "<a href="GmManualXmlRpcApi.html">slave mode</a>" if it is possible to get the source system to work with GNUmed. This is especially desirable if doctors are already using a billing or scheduling system that they may like to continue to use.
<p></p>
For most practices, proceeding with Step 1 should be co-ordinated with your plan to use the system for something more than just patient demographics. Typical minimum additional functionalities would be the tracking and maintaining of <ul>
<li> problem lists
</li> <li> allergies, immunizations and medications
</li> <li> incoming results (test data, reports)
</li></ul> 
<p></p>
As at February 2010, GNUmed manages problem lists and SOAP notes; provides the ability to record allergies; the input and printing of simple medication lists; the import and signing of digital documents; and manually inputting and signing test results. Batch importing of digital (lab) results has been specced out and is being gradually brought to fruition.
<p></p>
<h2><a name="Step_2:_Stop_adding_new_paper_to_the_old_paper_chart"></a>  Step 2: Stop adding new paper to the old paper chart </h2>
<p></p>
Before you even <em>begin</em> to worry about converting existing charts, you <em>must</em> first figure out how to stop <em>adding</em> paper to your charts. This means that you must develop a reliable system to intercept all incoming and internally-generated paper and to redirect and/or translate it and manage it inside a safe, secure and standards-compliant "digitized / digital documents workflow".
<p></p>
Do make sure you know your national legal and professional regulatory requirements for records retention and archiving before you spend time and effort converting, importing and archiving documents. The well-known <a href="http://www.alliancegroup.co.uk/pdf-searchable-images.htm" target="_top">Portable Document Format (PDF)</a> is not an image format, and could be judged inadmissible in the event of disputes over records of care. In some jurisdictions it may be necessary to preserve your images as TIFF files, despite what may look like redundancy if you should prefer to import PDF versions into the patient record. Do not lightly dismiss this consideration.
<p></p>
Approaches for various sources of new paper are offered:
<p></p>
<table rules="none" border="1" class="foswikiTable">
	<thead>
		<tr class="foswikiTableOdd foswikiTableRowdataBgSorted0 foswikiTableRowdataBg0">
			<th class="foswikiTableCol0 foswikiFirstCol"> <a rel="nofollow" href="/bin/rest/PublishPlugin/publish?validation_key=b6adb20ba63cfbada77bacf048ebff7c;topic=Gnumed.PublishManual;ping=29%20Jan%202014%20-%2015:24;sortcol=0;table=25;up=0#sorted_table" title="Sort by this column">Source</a> </th>
			<th class="foswikiTableCol1"> <a rel="nofollow" href="/bin/rest/PublishPlugin/publish?validation_key=b6adb20ba63cfbada77bacf048ebff7c;topic=Gnumed.PublishManual;ping=29%20Jan%202014%20-%2015:24;sortcol=1;table=25;up=0#sorted_table" title="Sort by this column">Solutions</a> </th>
			<th class="foswikiTableCol2 foswikiLastCol"> <a rel="nofollow" href="/bin/rest/PublishPlugin/publish?validation_key=b6adb20ba63cfbada77bacf048ebff7c;topic=Gnumed.PublishManual;ping=29%20Jan%202014%20-%2015:24;sortcol=2;table=25;up=0#sorted_table" title="Sort by this column">See</a> </th>
		</tr>
	</thead>
	<tbody>
		<tr class="foswikiTableEven foswikiTableRowdataBgSorted0 foswikiTableRowdataBg0">
			<td class="foswikiTableCol0 foswikiFirstCol"> all sources </td>
			<td class="foswikiTableCol1"> petition to be sent digital streams or files </td>
			<td align="center" class="foswikiTableCol2 foswikiLastCol"> regional advocates </td>
		</tr>
		<tr class="foswikiTableOdd foswikiTableRowdataBgSorted1 foswikiTableRowdataBg1">
			<td class="foswikiTableCol0 foswikiFirstCol"> incoming faxes </td>
			<td class="foswikiTableCol1"> efax services, or a fax server </td>
			<td align="center" class="foswikiTableCol2 foswikiLastCol"> <a href="FaxIntegration.html">Fax Integration</a> </td>
		</tr>
		<tr class="foswikiTableEven foswikiTableRowdataBgSorted0 foswikiTableRowdataBg0">
			<td class="foswikiTableCol0 foswikiFirstCol"> online data </td>
			<td class="foswikiTableCol1"> download or Save as or "Print" to a digital file </td>
			<td align="center" class="foswikiTableCol2 foswikiLastCol"> web search: <br>"Print to PDF" </td>
		</tr>
		<tr class="foswikiTableOdd foswikiTableRowdataBgSorted1 foswikiTableRowdataBg1">
			<td class="foswikiTableCol0 foswikiFirstCol foswikiLast"> unavoidable paper <br>(mailed or hand-delivered by patients or via doctors' bags) </td>
			<td class="foswikiTableCol1 foswikiLast"> image scan ± optically recognize </td>
			<td align="center" class="foswikiTableCol2 foswikiLastCol foswikiLast"> <a href="DocumentImaging.html">Document Imaging</a> </td>
		</tr>
	</tbody></table>
<p></p>
Keep a clear record of the date(s) on which you implemented the above changes in your praxis, and make sure all of your staff and doctors are aware. This will save a lot of trouble looking for information in the wrong places.
<p></p>
Congratulations! Your non-granular patient information is now GNUmed-attachable via the <a href="GmManualDocumentImporter.html">GmManualDocumentImporter</a> plugin. All that remains are your now "frozen" archival paper charts&#8230;
<p></p>
<h2><a name="Step_3:_Choose_how_much_archival_paper_to_import"></a>  Step 3: Choose how much archival paper to import </h2>
<p></p>
How much historical paper is worth scanning from each chart? One option would be to have the secretaries transcribe the inside cover "summary" information, where summaries already existed, from which the problem lists could be generated. Another would be to scan (e.g. into pdf) just the summary, or the entire chart, or anything in between the two.
<p></p>
However, unless all of the entirety of a patient's chart would be scanned, it will need to be retained somewhere and accessed as needed in conjunction with the electronically-maintained information, under a so-called "hybrid" model.
<p></p>
Scanning and filing patients' entire paper medical charts is a lot of work, and typically non cost-recoverable, except from private payers. The value proposition may be better at retirement compared to physical storage in trust with management fees. Patients have been offered the option to pay a fee to have their charts scanned, typical runs entailing 30 - 60 minutes' work for which (e.g.) students could be hired. A charge to the patient can in some jurisdictions be levied for "electronic archiving, pdf rendering and encrypted USB key preparation".
<p></p>
Tips: <ul>
<li> some doctors who move to an EMR use the first subsequent visit of each pre-existing patient to populate the EMR with a problem list and to identify "key pages" for scanning.
</li> <li> some suggest that the subset of pages that had been scanned be kept in a separate section at the front of each paper chart, in order to avoid later re-scanning what had already been scanned.
</li></ul> 
<p></p>
The transition can take between 6 months and two years. A lot of your processes (and those of the office staff) will need to be re-engineered.
<a name="TopicEnd"></a>
<p></p>
<p></p>
<p></p>
<p></p>
</div>
</body></html>

APT Browse - Built by Thomas Orozco.