# Family History

**URL:** <https://discourse.openehr.org/t/family-history/12029>\
**Category:** Clinical (archive)\
**Created:** [18 November 2004 01:52 UTC](https://discourse.openehr.org/t/family-history/12029 "2004-11-18T01:52:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sam](https://discourse.openehr.org/letter_avatar_proxy/v4/letter/s/5f9b8f/32.png) [@Sam](https://discourse.openehr.org/u/Sam)\
**Post date:** [18 November 2004 01:52 UTC](https://discourse.openehr.org/t/family-history/12029/1 "2004-11-18T01:52:13Z")

</div>

Amnon

Thanks - a very full email - I will do my best.

First, in openEHR the schema is constant - based on the reference information model - so we do not have schema's for the archetype. I do not have any data as yet as this archetype is not in use as yet.

> Anyway, as for the Family History archetype - I took a look at it and I'd  
> like to map it to what I'm doing in HL7 which is more genomic-oriented.  
> Anyway, in my design submission I usually send out the model, the  
> corresponding schema and a few XML samples but I know you don't like to see  
> RIM-stuff.... Do you have samples for your archetype? It helps making it  
> more concrete...

I am happy to see things that do not need Visio that I can make sense of - a gif or something.

> Just a quick question: you have a statement saying "code match {[ac0021]}  
> -- =Relationship(openEHR)  
> I wonder if that's an existing vocabulary of types of family  
> relationships... because I'm struggling with the existing HL7 vocab and how  
> to qualify it with a parental indication.

This is available as part of the editor - an XML file. This is a flat file of vocab domains essential for interoperability and for translating the GUI elements - 340 terms at the moment - shouldn't grow much from there as it is determined by the needs of the reference model. Archetypes carry their own terms if required. (see \terminology in the install directory)

> Further on, I'd like to try and add genomic data to this archetype - is  
> there a way to work on it together? Do you have a registry of archetypes?  
> I also think of showing it to the physician from Boston with whom I develop  
> the HL7 model - he is focused on the use case of BRCA.

Cool....I believe that it should be possible to spit out the RMIM specification from the editor - that would be really cool - IBM could benefit from that! We have worked hard to get something that clinicians can respond to.... long way to go but I think we are on the right track. Also, CEN is looking at incorporating ADL into the new 13606 standard as the standard way to represent archetypes.

Cheers, Sam