<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">445860545</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180317145441.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170323e20110701xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s00439-011-0992-y</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s00439-011-0992-y</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">Electronic medical records and personalized medicine</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Mark Hoffman, Marc Williams]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">If the dream of personalized medicine is to be realized, tremendous amounts of data specific to each individual must be captured, synthesized and presented to clinicians at the time this information is needed to make care decisions for the patient. This can only be accomplished through the use of sophisticated electronic medical record (EMR) systems that are designed to support this function. This article will define two important aspects of a fully functional EMR the ability to: present patients or clinicians with high quality context specific information at the point of care (so-called &quot;just-in time” education) and to combine clinically relevant information from disparate sources in order to guide the clinician to the optimized intervention for a given patient (clinical decision support). Personalized medicine examples are used to illustrate these concepts. As implemented most EMR systems are not being used to assimilate the information needed to provide personalized medicine. A description of necessary enhancements to currently available systems that will be needed to create a &quot;personalized medicine enabled” EMR is provided.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer-Verlag, 2011</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Hoffman</subfield>
   <subfield code="D">Mark</subfield>
   <subfield code="u">Research Solutions, Cerner Corporation, 2800 Rockcreek Parkway, 64117, Kansas City, MO, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Williams</subfield>
   <subfield code="D">Marc</subfield>
   <subfield code="u">Intermountain Healthcare, Clinical Genetics Institute, 324 10th Ave. Suite 183, 84103, Salt Lake City, UT, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Human Genetics</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">130/1(2011-07-01), 33-39</subfield>
   <subfield code="x">0340-6717</subfield>
   <subfield code="q">130:1&lt;33</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">130</subfield>
   <subfield code="o">439</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s00439-011-0992-y</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s00439-011-0992-y</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Hoffman</subfield>
   <subfield code="D">Mark</subfield>
   <subfield code="u">Research Solutions, Cerner Corporation, 2800 Rockcreek Parkway, 64117, Kansas City, MO, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Williams</subfield>
   <subfield code="D">Marc</subfield>
   <subfield code="u">Intermountain Healthcare, Clinical Genetics Institute, 324 10th Ave. Suite 183, 84103, Salt Lake City, UT, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Human Genetics</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">130/1(2011-07-01), 33-39</subfield>
   <subfield code="x">0340-6717</subfield>
   <subfield code="q">130:1&lt;33</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">130</subfield>
   <subfield code="o">439</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
