Deprecated: implode(): Passing glue string after array is deprecated. Swap the parameters in /data/lib/bibtex.lib.php on line 28
@article {loinc-389, author = {Staes, Catherine J and Huff, Stanley M and Evans, R Scott and Narus, Scott P and Tilley, Cyndalynn and Sorensen, John B}, title = {Development of an information model for storing organ donor data within an electronic medical record.}, journal = {Journal of the American Medical Informatics Association : JAMIA}, abstract = {To develop a model to store information in an electronic medical record (EMR) for the management of transplant patients. The model for storing donor information must be designed to allow clinicians to access donor information from the transplant recipient's record and to allow donor data to be stored without needlessly proliferating new Logical Observation Identifier Names and Codes (LOINC) codes for already-coded laboratory tests. Information required to manage transplant patients requires the use of a donor's medical information while caring for the transplant patient. Three strategies were considered: (1) link the transplant patient's EMR to the donor's EMR; (2) use pre-coordinated observation identifiers (i.e., LOINC codes with *(wedge)DONOR specified in the system axes) to identify donor data stored in the transplant patient's EMR; and (3) use an information model that allows donor information to be stored in the transplant patient's record by allowing the "source" of the data (donor) and the "name" of the result (e.g., blood type) to be post-coordinated in the transplant patient's EMR. We selected the third strategy and implemented a flexible post-coordinated information model. There was no need to create new LOINC codes for already-coded laboratory tests. The model required that the data structure in the EMR allow for the storage of the "subject" of the test. The selected strategy met our design requirements and provided an extendable information model to store donor data. This model can be used whenever it is necessary to refer to one patient's data from another patient's EMR.}, year = {2005}, issn = {1067-5027}, pages = {357-63}, month = {May-Jun}, volume = {12}, pmid = {15684132} }