1.1<\/b> Main purpose<\/p>\n
The purpose of this Technical Specification is to specify a categorial structure<\/b>, within the subject field of patient findings and problems, by defining a set of common domain constraint<\/b>s for use within terminological systems including a classification, coding scheme, coding system, reference terminology and clinical terminology.<\/p>\n
Clinical findings are concept<\/b>s that are recorded in clinical records and can describe any state observed directly or indirectly concerning a patient and their relationship with the environment. This Technical Specification is focused on a sub-population of these findings concerning in vivo<\/i> descriptions of state (structure and function) directly related to the patient. This class of concept<\/b>s includes:<\/p>\n diseases, which may be defined as a state caused by a known or assumed pathological process impairing the normal physiological function and\/or anatomical structure affecting all or part of a patient, where a specific pathological change is caused by a defined mechanism;<\/p>\n<\/li>\n findings of state or function (including normal findings) observed directly relating to a patient.<\/p>\n<\/li>\n<\/ul>\n This Technical Specification describes a concept system detailing a domain constraint of sanctioned characteristics each composed of a semantic link and an applicable characterizing category.<\/p>\n The potential uses for this concept<\/b>ual framework are to:<\/p>\n support developers of new terminology systems concerning patient findings and problems;<\/p>\n<\/li>\n support developers of new detailed content areas of existing terminology systems concerning patient findings and problems to ensure conformance;<\/p>\n<\/li>\n facilitate the representation of patient findings and problems using a standard core model in a manner suitable for computer processing;<\/p>\n<\/li>\n provide a concept<\/b>ual framework for the generation of compositional concept representation<\/b> of patient findings and problems;<\/p>\n<\/li>\n facilitate the mapping<\/b> and improved semantic correspondence<\/b> between different terminologies by proposing a core specification for patient findings and problems;<\/p>\n<\/li>\n provide a core model to describe the structure of patient findings and problems, and facilitate improved semantic correspondence<\/b> with information models.<\/p>\n<\/li>\n<\/ul>\n 1.2<\/b> Target groups<\/p>\n The target groups for this Technical Specification are:<\/p>\n developers of terminology systems concerning patient findings and problems;<\/p>\n<\/li>\n developers of information systems that require a structured framework of concept<\/b>s to facilitate implementation;<\/p>\n<\/li>\n IT specialists, analysts and epidemiologists who require common models of knowledge to facilitate analysis of current and legacy data from one or more information systems;<\/p>\n<\/li>\n clinicians and coders to provide greater consistency in structure and organization when entering and retrieving data using one or more terminology systems;<\/p>\n<\/li>\n managers and administrative personnel in providing a benchmark by which to judge terminology solutions: as to whether the potential options will deliver compatibility with legacy data and future proofing to emerging terminology products.<\/p>\n<\/li>\n<\/ul>\n 1.3<\/b> Topics considered outside the scope<\/p>\n Topics considered outside the scope of this Technical Specification include:<\/p>\n a comprehensive categorial structure<\/b> for clinical findings;<\/p>\n<\/li>\n laboratory findings (including biochemical and histological results);<\/p>\n<\/li>\n signal findings (including the output from imaging and electrophysiological tests);<\/p>\n<\/li>\n social findings;<\/p>\n<\/li>\n the absence of findings, e.g. absent bowel sounds, the absence of a knee reflex, are not included within this Technical Specification as it might prejudice subsequent attempts at standardizing the modelling of such instances;<\/p>\n<\/li>\n an exhaustive list of all possible characterizing concept<\/b>s that could be used to describe clinical findings.<\/p>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":" Health informatics. Conceptual framework for patient findings and problems in terminologies<\/b><\/p>\n\n
\n
\n
\n
\n\n
\n Published By<\/td>\n Publication Date<\/td>\n Number of Pages<\/td>\n<\/tr>\n \n BSI<\/b><\/a><\/td>\n 2010<\/td>\n 22<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":348774,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[704,2641],"product_tag":[],"class_list":{"0":"post-348771","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-35-240-80","7":"product_cat-bsi","9":"first","10":"instock","11":"sold-individually","12":"shipping-taxable","13":"purchasable","14":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/348771","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/348774"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=348771"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=348771"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=348771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}