Statements in which the resource exists.
SubjectPredicateObjectContext
pubmed-article:8947775rdf:typepubmed:Citationlld:pubmed
pubmed-article:8947775lifeskim:mentionsumls-concept:C0026339lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C0995158lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C0026336lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C1511726lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C0808080lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C0205195lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C1550548lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C1555714lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C1705654lld:lifeskim
pubmed-article:8947775lifeskim:mentionsumls-concept:C1705922lld:lifeskim
pubmed-article:8947775pubmed:dateCreated1997-1-28lld:pubmed
pubmed-article:8947775pubmed:abstractTextThe capture of patient data in a structured format receives increasing attention. Data can be extracted from free text using natural language processing techniques, but it can also be collected in a structured fashion at the time of data entry. The latter has the advantage that completeness and unambiguity can be promoted by offering predefined terms and options for description of findings. The paper discusses two models for supporting structured data entry. In the direct model, there is an immediate relationship between the terms and options for data entry and the structure of the underlying database. In the indirect model, terms and options for data entry are based on a controlled vocabulary and not directly related to the structure in which actual data is represented. Both models have been utilized by ORCA (Open Record for CAre). We discuss the pros and cons of these two models in relation to the type of patient data and the task involved. It is concluded that a strategic combination of both models has more strengths and less weaknesses than the use of each model only.lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:commentsCorrectionshttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:languageenglld:pubmed
pubmed-article:8947775pubmed:journalhttp://linkedlifedata.com/r...lld:pubmed
pubmed-article:8947775pubmed:citationSubsetIMlld:pubmed
pubmed-article:8947775pubmed:statusMEDLINElld:pubmed
pubmed-article:8947775pubmed:issn1091-8280lld:pubmed
pubmed-article:8947775pubmed:authorpubmed-author:van...lld:pubmed
pubmed-article:8947775pubmed:issnTypePrintlld:pubmed
pubmed-article:8947775pubmed:ownerNLMlld:pubmed
pubmed-article:8947775pubmed:authorsCompleteYlld:pubmed
pubmed-article:8947775pubmed:pagination797-801lld:pubmed
pubmed-article:8947775pubmed:dateRevised2009-11-18lld:pubmed
pubmed-article:8947775pubmed:meshHeadingpubmed-meshheading:8947775-...lld:pubmed
pubmed-article:8947775pubmed:meshHeadingpubmed-meshheading:8947775-...lld:pubmed
pubmed-article:8947775pubmed:meshHeadingpubmed-meshheading:8947775-...lld:pubmed
pubmed-article:8947775pubmed:meshHeadingpubmed-meshheading:8947775-...lld:pubmed
pubmed-article:8947775pubmed:meshHeadingpubmed-meshheading:8947775-...lld:pubmed
pubmed-article:8947775pubmed:year1996lld:pubmed
pubmed-article:8947775pubmed:articleTitleStructured data entry in ORCA: the strengths of two models combined.lld:pubmed
pubmed-article:8947775pubmed:affiliationDepartment of medical Informatics, Erasmus University, Rotterdam, The Netherlands. vonginneken@mi.fgg.eur.nllld:pubmed
pubmed-article:8947775pubmed:publicationTypeJournal Articlelld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:8947775lld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:8947775lld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:8947775lld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:8947775lld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:8947775lld:pubmed
http://linkedlifedata.com/r...pubmed:referesTopubmed-article:8947775lld:pubmed