Use to create a framework for recording answers to pre-defined screening questions about health-related problems found in both genetic and non-genetic family members.
Traditionally the scope of family history has been focused on identifying factors or biomarkers in genetically related family members. Non-genetic family members may also be included, such as adopted or long term fostered children, those related by marriage, or other unrelated individuals who participate in the regular life and influence of the family.
The intended scope of this archetype is to include the broadest range of problems or issues that might be found within families. It includes problems or diagnoses that are:
- genetically inheritable, such as breast cancer or Huntington’s disease
- not genetically inheritable but influenced by psychological, social, or environmental factors related to the family, such as exposure to toxins in the family home, domestic violence, sexual abuse, alcoholism and other addictions.
This archetype has two discrete approaches for screening for family history:
- All relationships - Does anyone in the family have ‘Problem/diagnosis name’?
- Specified relationship - Does your 'Relationship' have ‘Problem/diagnosis name’?
Common use cases include, but are not limited to:
- Systematic questioning in any consultation, for example:
--- Is there a history of heart disease in the family?
--- Is there a history of mental health problems in the family?
--- Is there a history of addiction in the family?
--- Did your mother have diabetes? - Specific questioning related to chronic disease management or preventive health.
Templates for specific use cases may be constrained to relationships with genetic family members if required.
The semantics of this archetype are intentionally loose, and querying this archetype would normally only be useful or safe within the context of each specific template. In a template, each data element would usually be renamed to the specific question asked. Where value sets have been proposed for common use cases, these can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case.
Use separate EVENTs to specify whether the questions relate to a point in time or an interval of time. For example: "Do any family members have COVID now?" as a point in time EVENT and "Have any family members had COVID during the past 4 weeks?" as an interval EVENT.
The source of the information in a questionnaire response may vary in different contexts but can be specifically identified using the 'Information provider' element in the Reference Model.
This archetype has been designed to be used as a screening tool or to record simple questionnaire-format data for use in situations such as a disease registry. If the screening questionnaire identifies the presence of a health concern in a family member, it is recommended that the clinical system record the specific details using the EVALUATION.family_history archetype or the CLUSTER.family_prevalence archetype.
Organització: Helse Vest IKT AS
Correu electrònic: marit.alice.venheim@helse-vest-ikt-no
Data d'autor original: 2020-08-20
Organització: Helse Vest IKT AS
Correu electrònic: marit.alice.venheim@helse-vest-ikt-no
Data d'autor original: 2020-08-20
- Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
- Custodian Organisation: openEHR Foundation
- Original Namespace: org.openehr
- Original Publisher: openEHR Foundation
- Custodian Namespace: org.openehr
- MD5-CAM-1.0.1: 726282DF184EE57A937A54D9EAE46D13
- Build Uid: 9ba86842-e1ee-4201-bfc9-41f2247e68e7
- Ip Acknowledgements: This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyrighted material of the International Health Terminology Standards Development Organisation (IHTSDO). Where an implementation of this artefact makes use of SNOMED CT content, the implementer must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/snomed-ct/get-snomed or info@snomed.org.
- Revision: 1.0.0
This data element is intended to provide collection context for the question/answer groups when queried at a later date. It is not expected that this data element will be exposed to the individual, but only stored in data. For example: pre-admission screening or the name of the actual questionnaire.
'Problem/Diagnosis name' has been made mandatory as it is the sole focus of the question with no further details anticipated. For example: “Does anyone in the family have diabetes?”.
For example: 'Colorectal cancer' or 'Cancer'; 'Angina' or 'Cardiovascular disease'. Coding of the 'Problem/diagnosis name' with a terminology is preferred, where possible.
In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. In cases where an individual is adopted and no information is available, it is recommended to record 'Unknown'. For example: Does any in your family have diabetes?
Elecció de:
Coded Text
Text
Boolean
‘Relationship’ is the focus of the question, and in order to answer the question both the 'Relationship' and the 'Problem/diagnosis name' need to be mandatory. For example: 'Does your father have diabetes?' or 'Have any of your first degree relations had colorectal cancer?'
For example: First degree relative, mother, step-father, maternal grandmother, or paternal uncle. Coding of the relationship with a terminology is preferred, where possible and including specification of maternal and paternal as required.
Coding of the 'Problem/diagnosis name' with a terminology is preferred, where possible.
In a template, the data element would usually be renamed to the specific question asked. The proposed value set can be adapted for local use by using the DV_TEXT or the DV_BOOLEAN datatypes choice to match each specific use case. In cases where an individual is adopted and no information is available, it is recommended to record 'Unknown'. For example: Does your father have diabetes?
Elecció de:
- Coded Text
- Text
- Boolean
The 'Timing' data element has deliberately been loosely modelled to support the myriad of ways that it can be used in questionnaires to capture when an issue, problem or diagnosis occured. The specific and intended semantics can be further clarified in a template. For example: the actual date and/or time; the start and stop time for when the issue, problem or diagnosis occured; the interval of time during which the issue, problem or diagnosis occured; the duration of the issue, problem or diagnosis; the age of the individual at the time of the issue, problem or diagnosis; or the duration of time since it occurred. A partial date is valid, using the DV_DATE_TIME data type, to record only a year.
Elecció de:
Date/Time
Interval of Date/Time
Duration
Interval of Duration
- Text
Incloure:
Tots arquetips no exclosos explícitament
Incloure:
Tots arquetips no exclosos explícitament
For example: local information requirements or additional metadata to align with FHIR.
Incloure:
Tots arquetips no exclosos explícitament
Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)
SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India
Hugo Claudio Briceño García, Catsalut, Spain
Clara Calleja Vega, CatSalut. Servei Català de la Salut., Spain
Christian Chevalley, ADOC, Thailand
Giovanni Delussu, crs4, Italy
Mona Didriksen, Helse Vest IKT, Norway
Manuela Domingo, hospital general universitario dr. balmis, Spain
Gunn Elin Blakkisrud, DIPS ASA, Norway
Aleksander Furnes, Helse Nord IKT, Norway
Ciprian Gerstenberger, HN IKT, Norway
Rosane Gotardo, Systema Ltda., Brazil
Heather Grain, Llewelyn Grain Informatics, Australia
Atle Hansen, Universitetssykehuset Nord-Norge, Norway
Evelyn Hovenga, EJSH Consulting, Australia
Susanna Jönsson, Region Värmland, Sweden
Mika Kiviaho, Tietoevry Care, Finland
June Marie Nepstad Knappskog, Helse Nord IKT AS, Norway (openEHR Editor), Norway
Martin Koch, Servei Català de la Salut, Spain
Ronald Krawec, Alberta Health Services, Canada
Lise Kristin Knutsen, Oslo universitetssykehus, Norway
Anjali Kulkarni, Karkinos, India
Kanika Kuwelker, Helse Vest IKT, Norway
Jörgen Kuylenstierna, eWeave AB, Sweden
Eli Larsen, UNN, Norway
Liv Laugen, Oslo University Hospital, Norway, Norway (openEHR Editor)
Darin Leonhardt, PLRI für medizinische Informatik/ Medizinische Hochschule, Germany
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Ruth Lochan, Akademiska Sjukhuset Uppsala, Sweden
Michael Lutz, BITsoft, Germany
Hanne Marte Bårholm, Helse Vest IKT, Norway (openEHR Norway redaktør)
Ian McNicoll, freshEHR Clinical Informatics, United Kingdom
Arunakiry Natarajan, medondo, Germany
Svenne Naumann, Finnmarkssykehuset, Norway
Olha Nikolaieva, University Hospital Basel, Switzerland
Terje Nordberg, Helse Bergen, Norway
Mikael Nyström, Cambio Healthcare Systems AB, Sweden
Marlene Pérez Colman, Digital Health and Care Wales, United Kingdom
Benjamin Senst, Germany
Andre Smitt-Ingebretsen, Sørlandet sykehus HF, Norway
Norwegian Review Summary, Norwegian Public Hospitals, Norway
John Tore Valand, Helse Vest IKT, Norway (openEHR Editor)
Wouter Zanen, Eurotranplant, Netherlands
- alemany: Henning Schmidt, Darin Leonhardt, Martin Koch, Medizinische Hochschule Hannover, PLRI für medizinische Informatik/ Medizinische Hochschule, Servei Català de la Salut, hschmidt@n-z-a.de, leonhardt.darin@mh-hannover.de, martinandreaskoch@catsalut.cat
- Bokmål noruec: Silje Ljosland Bakke, Marit Alice Venheim, John Tore Valand, Liv Laugen, Vebjørn Arntzen, Hanne Marte Bårholm, Kanika Kuwelker, Helse Vest IKT AS, Helse Bergen, Oslo University Hospital, Norway, silje.ljosland.bakke@helse-vest-ikt.no, marit.alice.venheim@helse-vest-ikt.no, john.tore.valand@helse-bergen.no, john.tore.valand@helse-vest-ikt.no, liv.laugen@ous-hf.no, varntzen@ous-hf.no, hanne.marte.sandal.barholm@helse-vest-ikt.no, kanika.kuwelker@helse-vest-ikt.no