WO2013055972A1

WO2013055972A1 - Genogram mobile method and apparatus

Info

Publication number: WO2013055972A1
Application number: PCT/US2012/059829
Authority: WO
Inventors: Daniel LAKIER; Parvathi SRINIVASAN
Original assignee: Redmane Technologies, Llc.
Priority date: 2011-10-11
Filing date: 2012-10-11
Publication date: 2013-04-18

Abstract

Embodiments include a system, device, method and computer-readable medium to use genograms to document relationships between entities or parties. Aspects of the disclosure relate in general to a mobile application to track relationships. Aspects include an apparatus, system, method and computer-readable storage medium to use genograms to document relationships between entities or parties.

Description

PCT PATENT APPLICATION - GENOGRAM MOBILE METHOD AND

APPARATUS

BACKGROUND

Field of the Invention

[0001] Aspects of the disclosure relate in general to a mobile application to track relationships. Aspects include an apparatus, system, method and computer-readable storage medium to use genograms to document relationships between entities or parties.

"Description of the Related Art"

[0002] When child protective services investigates a potential situation, a social worker generally arrives at the scene with a case file. Sometimes the case file is very complete, and other times the case file is far from complete. During the latter, social workers will arrive at a location knowing very little about the situation.

SUMMARY

[0003] Embodiments include a system, device, method and computer-readable medium to use genograms to document relationships between entities or parties.

BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 illustrates male to left of female.

[0005] FIG. 2 depicts children of different ages.

[0006] FIG. 3 illustrates multiple spouses.

[0007] FIG. 4 is a multi-level diagram of a family structure.

[0008] FIG. 5 illustrates higher level rule taking precedence.

[0009] FIG. 6 illustrates a Level Positioning Process embodiment.

[0010] FIG. 7A displays a genogram before adding John as spouse to Jane.

[0011] FIG. 7B shows a genogram after adding John as spouse to

Jane.

[0012] FIG. 8 shows a genogram after adding John's younger parents.

[0013] FIG. 9 illustrates positioning of an unrelated member.

[0014] FIG. 10 displays a screen flow of an embodiment.

[0015] FIG. 1 1 illustrates a main view screen of an embodiment.

[0016] FIG. 12 illustrates an icon change view screen of an embodiment.

[0017] FIG. 13 illustrates an example select family screen

embodiment.

[0018] FIG. 14 illustrates an add new family screen embodiment.

[0019] FIG. 15 illustrates an edit family details screen embodiment.

[0020] FIG. 16 illustrates a delete family confirmation dialog embodiment.

[0021] FIG. 17 illustrates a reset family confirmation dialog embodiment.

[0022] FIG. 18 illustrates an add a person screen embodiment. [0023] FIG. 19 illustrates an edit a person details screen

embodiment.

[0024] FIG. 20 illustrates a characteristic picker screen

embodiment.

[0025] FIG. 21 illustrates a person quick info screen embodiment.

[0026] FIG. 22 illustrates a family relationships screen

embodiment.

[0027] FIG. 23 illustrates an abuse relationship screen

embodiment.

[0028] FIG. 24 illustrates a parent relationship screen embodiment.

[0029] FIG. 25 illustrates a child relationship screen embodiment.

[0030] FIG. 26 illustrates a support relationship screen

embodiment.

[0031] FIG. 27 illustrates an other relationship screen embodiment.

[0032] FIG. 28 illustrates an add relationship screen embodiment.

[0033] FIG. 29 illustrates an edit relationship screen embodiment.

[0034] FIG. 30 illustrates a select relationship screen embodiment.

[0035] FIG. 31 illustrates a relationship reset screen embodiment.

[0036] FIG. 32 illustrates a select household screen embodiment.

[0037] FIG. 33 illustrates an add new household screen

embodiment.

[0038] FIG. 34 illustrates a select household members screen embodiment.

[0039] FIG. 35 illustrates an edit household details screen embodiment.

[0040] FIG. 36 illustrates a delete household confirmation screen embodiment.

[0041] FIG. 37 illustrates an electronic mail screen embodiment.

[0042] FIG. 38 illustrates a print screen embodiment.

[0043] FIG. 39 illustrates a data model of the embodiment.

[0044] FIG. 40 illustrates block diagram of the embodiment. DETAILED DESCRIPTION

[0045] One aspect of the disclosure includes the realization that genograms may be used in social services to diagram family and other relationships between individuals impacting the life of a client or prospective client. Such genograms may be known as a McGoldrick-Gerson study or a Lapidus Schematic.

[0046] Embodiments of the present disclosure include a tool capable of producing genograms in a tablet device. The format of this device allows genograms to be produced electronically in the home of the client which is far more efficient than preparing them on paper. This application allows existing genograms to be updated and also allows for formal genograms to be produced in the field without requiring re-entry of data upon returning from the field. Genograms typically document relationships with a focus on negative interactions.

[0047] In some embodiments, the genogram notation has been extended to allow for the documenting of supportive relationships - a key mechanism for creating a sustainable client enhancement plan.

[0048] Embodiments will now be disclosed with reference to a block diagram of an exemplary social service tablet 4000 of FIG. 40, constructed and operative in accordance with an embodiment of the present disclosure. Social service tablet 4000 is configured to merge balances of payment cards 100.

[0049] Social service tablet 4000 may run a multi-tasking operating system (OS) and include at least one processor or central processing unit (CPU) 4100, a non-transitory computer- readable storage medium 4200, and a display 4300.

[0050] Processor 2100 may be any central processing unit, microprocessor, micro-controller, computational device or circuit known in the art.

[0051] It is well understood by those in the art, that the elements of FIG. 40 may be implemented as hardware, firmware, or as software instructions and data encoded on a non-transitory computer-readable storage medium 2200.

[0052] As shown in FIG. 40, processor 4100 is functionally comprised of a social service program 41 10, application interface 4130, and a data processor 4130.

[0053] Social service program 41 10 may further comprise a relationship tracker 41 12 and genogram mapper 41 14. Relationship tracker allows for users to add persons and track relationships between persons.

Genogram mapper allows the social service program 41 14 to graphically illustrate relationships from person data received by relationship tracker.

These structures may be implemented as hardware, firmware, or software encoded on a computer readable medium, such as storage media 2200.

Further details of these components are described with their relation to method embodiments below.

[0054] Data processor 4120 interfaces with storage media 2200 and display 4300. The data processor 4120 enables processor 2100 to locate data on, read data from, and write data to, these components.

[0055] Application interface 4130 is any graphical user interface known in the art.

[0056] Display 4300 may be any display device known in the art.

[0057] Computer-readable storage media 4200 may be a

conventional read/ write memory such as a magnetic disk drive, floppy disk drive, optical drive, compact-disk read-only-memory (CD-ROM) drive, digital versatile disk (DVD) drive, high definition digital versatile disk (HD-DVD) drive, Blu-ray disc drive, magneto-optical drive, optical drive, flash memory, memory stick, transistor-based memory, magnetic tape or other computer-readable memory device as is known in the art for storing and retrieving data.

Significantly, computer-readable storage media 4200 may be remotely located from processor 4100, and be connected to processor 4100 via a network such as a local area network (LAN), a wide area network (WAN), or the Internet. [0058] In addition, as shown in FIG. 40, storage media 4200 may also contain a relationship database 4210. Relationship database 4210 is configured to store information associating persons with other persons.

[0059] It is well understood by those in the art, that the elements of FIGS. 1-39 may be implemented as hardware, firmware, or as software instructions and data encoded on a non-transitory computer-readable storage medium 4200.

[0060] An aspect of generating a Genogram is determining how to place icons on the map in the appropriate location. The process for placing the correct notation is described below.

[0061] The application places the various members of a family relative to one another based on the relationships that exists between them. It uses the 'Level Positioning' process to calculate the relative positions of all 'related' members (i.e.: members with at least one 'Family' relationship) on the screen. It then places all \inrelated 'members to the right of the right most related members at that level.

[0062] Positioning of 'Related' members

[0063] The 'Level Positioning' process is a top-down recursive process, used to fix the position of the various related members of the family on the screen. The positioning is based on:

[0064] The gender of the family member.

[0065] In same level relationships, 'Male' members are always placed to the left of their female relatives, as is shown in FIG. 1.

[0066] FIG. 2 depicts children of different ages. The type and date of relationship between any two family members is shown. Siblings are arranged in descending order of their date of birth.

[0067] Spouses are arranged in descending order of start date of relationship, as shown in FIG. 3.

[0068] FIG. 4 is a multi-level diagram of a family structure. Parents are at one level higher than their children.

[0069] In cases where more than one rule applies, the rules at a higher level take precedence over the rules at a lower level . For e.g.: If a family genogram represents a couple with their parents, the female will appear to the left of the male, if at the level prior (parents level) the parents of the female are to the left of the parents of the male.

[0070] FIG. 5 illustrates higher level rule taking precedence. The process supports adding only up to a spouse's spouse to the genogram. For e.g.: in extending FIG. 3, Mary and Jane can have spouses but these spouses cannot have their families represented on this genogram.

[0071] The process takes in following inputs:

[0072] 1. The level value - with the topmost level being level zero.

[0073] 2. The objects to be arranged at that level.

[0074] 3. The starting position, centered on which the objects will have to be arranged.

[0075] FIG. 6 illustrates a Level Positioning Process embodiment. The main factor in fixing the position of a person is whether a person is

'floating' or not. A person is defined as 'floating' if their position has not yet been fixed or if they do not have a higher level relative (no parents).

[0076] The process starts by creating the list of level 0 objects organized such that the first element is the oldest male member at level 0. If no male exists, the oldest female is the first element. Each element is then followed by all relatives at that level and so on. It traverses left to right through the list of input elements. For any two related elements at the same level, it reclusively calls the process for their children and the children's level relations.

[0077] Initially, the process receives the input list.

[0078] If not at the end of the input list, the process gets the next 'floating' person in input list.

[0079] If there is no spouse, the process fixes the position of the person, and this step is repeated.

[0080] The process gets all spouses of current person in descending order of start date of relationship. For each spouse we do the following:

[0081] If the spouse (sp l) is floating, get the list of spouse's spouse

(sp2) . [0082] If sp2 is floating (also includes current person), fix the position of sp2 based on the number of children between sp l and sp2.

[0083] If not floating, get next sp2.

[0084] For all sp l >sp2 relationships above, get the list of children in descending order of date of birth. For each child, determine level relations and place them after the child, in descending order of start date of

relationship. Recursively perform step 1 , for each child and its level relatives at the same level . The objects will be arranged relative to the midpoint between the two parents (sp l) and (sp2).

[0085] If spouse (sp l) is fixed, get next sp l .

For all current person >sp l relationships updated, get the list of children in descending order of date of birth. For each child, determine level relations and place them after the child, in descending order of start date of relationship. Recursively perform step 1 , for each child and its level relatives at the same level. The objects will be arranged relative to the midpoint between the two parent's current person and sp 1.

[0086] If the process is at the end of the input list, exit iteration for the input list.

[0087] Coordinate Calculation

[0088] The position of the first person for any iteration of the list, is calculated using the formula,

[0089] Position=startingPosition- (objectsToArrange.count*widthOfEachPersonOnScreen +

constantSpaceBetweenPeople*(objectsToArrange. count- 1)) / 2;

[0090] Where, startingPosition is center of screen for Level 0 and is the mid-point between two parents for subsequent levels.

[0091] For related persons in the input list, the coordinate is calculated as:

[0092] If no children,

[0093] Position= relatedPersonCoordinate+

widthOfEachPersonOnScreen+constantSpaceBetweenPeople

[0094] If children (number of children=n) exist, [0095] Position= relatedPersonCoordinate +

(widthOfEachPersonOnScreen+constantSpaceBetweenPeople)*n

[0096] Sample Scenario

[0097] Below, are some example scenarios that illustrate the working of the level positioning process.

[0098] EXAMPLE 1. Placement of spouse with no higher level relations To explain the process, let us take the example of placement of spouse with no higher level relations.

[0099] The example walks through the scenario of adding a spouse (with no relations) to a person with higher level relatives. FIG. 7A displays a genogram before adding John as spouse to Jane.

[00100] When the user adds a spouse 'John Doe' to 'Jane Smith', the process places the family members using the following steps:

[00101] 1. Start with an input list: John Smith, Josephine since John and Josephine are the only two level 0 members with John being the oldest male.

[00102] 2. Calculate the position of John Smith (floating since he has no higher level relations and his position has not yet been fixed) with respect to the center of the screen (since he is the first person at level 0).

[00103] 3. Check for spouse and finds a floating spouse

Josephine Smith.

[00104] 4. Check for Josephine Smith's floating spouses. Since none exist, fixes the position of Josephine Smith based on the number of children & relations between John and Josephine.

[00105] 5. For each child (in case, only one Jane Smith) and her level relations (the newly added 'John Doe') repeats steps 1 through 5.

[00106] 6. Since no other level 0 members exist and all members have been fixed, the process exits.

[00107] The resulting positioning of the family members is shown in FIG. 7B. With 'John Doe' placed to the left of 'Jane Smith' maintaining gender rules.

[00108] Example 2: Placement of spouse with higher level relations [00109] Example 2 walks through the scenario of adding a spouse with higher level relations to a person also with higher level relatives. It starts at the point left off at the previous example. The process adds parents to spouse 'John Doe'. It illustrates how the higher level relationship (parents in descending order of age), takes precedence over maintaining lower level rules (male left of female) .

[00110] When the user adds a parents 'Ed Doe' to 'Maureen Doe' to 'John Doe', the process places the family members using the following steps:

[00111] The process starts with ordered input list: John Smith, Josephine Smith, Ed Doe and Maureen Doe since is the oldest male.

[00112] The process fixes the position of John and Josephine Smith as outlined above and starts a second recursion with 'Jane Smith' and 'John Doe'.

[00113] While processing the input list: 'Jane Smith' and 'John Doe', the process determines that 'John Doe' is not floating (by virtue of a higher level relative), so it skips fixing the position of 'John Doe'. The process fixes the position of the child -'Jane Doe' and returns to level 0 input list processing since 'Jane Doe' does not have other spouses.

[00114] The process checks ED Doe and Maureen Doe. Since there are floating, fixes their position and starts processing of their child and their level relations: 'Jane Smith' and 'John Doe'.

[00115] The process then checks and determines that 'Jane Smith' is fixed.

[00116] The process checks 'John Doe', and determines that he is floating (by virtue of position not being fixed), and fixes his position.

[00117] The process checks for other spouse of John, and finds

None.

[00118] For each relationship between John and his spouses (in this case just 'Jane Smith'), the process checks for children. Finding no children, the process returns to the level 0 recursion.

[00119] Since no other level 0 members exist and all members have been fixed, the process exits. [00120] The resulting positioning of the family members is shown in FIG. 8.

[00121] Once all the 'related' members have been placed, the process calculates the position of the \inrelated' members for each level starting the calculation at the right most related member's position at that level.

[00122] FIG. 9 illustrates the positioning of unrelated member - 'Frank Gait', to the right of the last member at that level (in this case: level 0)..

[00123] FIG. 10 displays a screen flow of an embodiment. A screen or menu item is represented as a box in the diagram. An arrow between two boxes indicates that a user can navigate from the screen or menu item from which the arrow originates by the description on that line, to the screen or menu item to which the arrow points. While not shown, the user can generally return to where they came from, should they need to.

[00124] We now turn to FIGS. 1 1-38 which depict screens of an embodiment process.

[00125] FIG. 1 1 illustrates a main view screen of an embodiment. This is the primary screen for viewing and maintaining genograms within the system. It includes a scrollable portal for viewing the diagram and a toolbar for performing actions within the system.

[00126] The toolbar may have buttons mapped to a variety of functions. Such buttons may include:

[00127] Icon Change Button: Navigates to the Icon Change screen. Allows the user to toggle between standard genogram view and a more traditional "family tree" style view

[00128] Clear Page Button: Clears the genogram view without deleting the database of people referenced by the genogram.

[00129] Print Button: Prints the genogram using Air Print.

[00130] Legend Button: Displays a legend describing the meaning of each of the symbols on the screen.

[00131] Email Button: Opens a new email message window and attaches a PDF of the genogram. [00132] Households Button: Navigates to the Select Household screen. Used to define groups of people living in the same household.

[00133] Genogram Name Label: Label indicating the name of the genogram currently being edited.

[00134] Maintain Genogram Button: Button that allows editing of high-level information about the genogram.

[00135] Change Family Button: Navigates to the Select Family screen. Used to open another genogram that has been saved on the device.

[00136] Reset Family Button: Removes all relationships currently associated with the current genogram.

[00137] FIG. 12 illustrates an icon change view screen of an embodiment. This screen allows the user to change the icons from a

Traditional' icon set, which is used more towards personal users, to a 'Genogram' icon set, which is used more towards social workers.

[00138] In this embodiment, the icon change view screen has two buttons.

[00139] Traditional Button: If not already active in the application, this button will set the icon set as Traditional'

[00140] Genomap Button: If not already active in the application, this button will set the icon set as 'Genomap'

[00141] FIG. 13 illustrates an example select family screen embodiment. This screen shows the user selectable families that have been previously created and saved. Here the user can quickly load up the family's genogram.

[00142] FIG. 14 illustrates an add new family screen embodiment. This screen allows the user to enter a new family's details. This is the beginning step to creating a genogram. All the relationship screens are found by long pressing a participant in the genogram.

[00143] The user may be prompted to enter a number of fields. These fields include a family name field and a description field.

[00144] Family Name: Text field to enter a family's name. [00145] Description: Text field to enter any extra info describing the family the user desires.

[00146] Done Button: This submits the entered family data and directs to a "Add new person" screen.

[00147] Cancel Button: This cancels the current input data.

[00148] FIG. 15 illustrates an edit family details screen embodiment. This screen allows the user to edit the family's details, such as family name and description. It is launched by pressing the 'Edit Family Details' button from the toolbar. This screen may also allow the user to delete the current family records entirely. A delete family confirmation dialog is shown at FIG. 16; this screen offers a layer of protection against accidentally deleting the family.

[00149] FIG. 17 illustrates a reset family confirmation dialog embodiment. This screen will allow the user to delete all the people and relationships from the genogram. The family remains, however.

[00150] FIG. 18 illustrates an add a person screen embodiment which allows the user to add a person and define their details. Details may include:

[00151] First Name Field: (Required Field) A person's first name.

[00152] MI Field: A person's middle initial.

[00153] Last Name Field: (Required Field) A person's last name.

[00154] Gender Button: (Required Selection) A person's gender.

[00155] Year/Date of Birth Field: A person's date of birth. Entered either with just the year, or the full date.

[00156] Year/Date of Death Field: A person's date of death. Entered either with just the year, or the full date.

[00157] Age Field: A person's numerical age. Only available to enter if there is no date entered in the Date of birth field.

[00158] Notes Field: An area to enter a note concerning the person.

[00159] Image Field: An image picker to select a picture for a person.

[00160] Characteristics Picker: Allows the user to pick appropriate characteristics that best describe the person. [00161] FIG. 19 illustrates an edit a person details screen

embodiment, which allows the user to edit a person's details. The editable fields include all the fields mentioned above.

[00162] FIG. 20 illustrates a characteristic picker screen

embodiment. In some embodiments, the characteristics may be predetermined from a list created by the user.

[00163] FIG. 21 illustrates a person quick info screen embodiment. This screen gives a pop-up dialog that contains quick info about the person. The user can edit relationships this person is a part of and also the user can edit the person's details. It may be launched by double tapping a participant in the genogram. The fields may include:

[00164] Name: Non-editable field that displays the person's full name.

[00165] Age: Non-editable field that displays a numeric

representation of the person's name.

[00166] Gender: Non-editable field that displays the person's gender.

[00167] DOB: Non-editable field that displays the person's date of birth in the format of MM-DD-YYYY

[00168] DOD: Non-editable field that displays the person's date of death in the format of MM-DD-YYYY

[00169] Notes: Non-editable field that displays any related notes about this person.

[00170] Edit Relationships Button: This button launches the 'Edit Relationship' screen.

[00171] Edit Person Details Button: This button launches the 'Edit Person Details' screen.

[00172] FIG. 22 illustrates a family relationships screen

embodiment. This screen shows 3 types of relationships for Family situations that can be associated between two participants in the genogram. The user may select one of three Family Relationships: Other, Marriage, and Common- Law Marriage. [00173] FIG. 23 illustrates an abuse relationship screen embodiment. This screen allows one to select an abuse relationship to be associated between two participants in the genogram. The user can select one of 6 abuse relationships: Sexual Abuse Perpetrator, Emotional Abuse

Perpetrator, Physical Abuse Perpetrator, Sexual Abuse Victim, Emotional Abuse Victim, and/or Physical Abuse Victim.

[00174] FIG. 24 illustrates a parent relationship screen embodiment. This screen allows the user to select on parent relationship between two participants in the genogram. Here the user can select one of two parent relationships: Biological Parents or Adoptive Parents.

[00175] FIG. 25 illustrates a child relationship screen embodiment. This screen allows the user to select a child relationship between two

participants in the genogram. Here the user can select one of two child relationships: Adopted Child or Biological Child.

[00176] FIG. 26 illustrates a support relationship screen

embodiment. This screen allows the user to select one support relationship to associate between two participants in a genogram. In this embodiment, the user can select one of eight support relationships:

[00177] Preventative Health Practices Provider,

[00178] Supportive Relationship Provider,

[00179] Emotional Stability Provider,

[00180] Sufficient Resources Provider,

[00181] Preventative Health Practices Receiver,

[00182] Supportive Relationship Receiver,

[00183] Emotional Stability Receiver, or

[00184] Sufficient Resources Receiver.

[00185] FIG. 27 illustrates an "other" relationship screen embodiment. This screen allows the user to select a Other' relationship that does not fall in the other relationship areas. Example "other" relationships include: Here the user can select one of five other relationships: Hostile, Close, Close-Hostile, Cut-Off, or Distant. [00186] FIG. 28 illustrates an add relationship screen embodiment. This screen allows the user to enter the details of a relationship between two participants. Fields may include the start date or end date of the relationship.

[00187] FIG. 29 illustrates an edit relationship screen embodiment. This screen allows the user to edit the details of a relationship.

[00188] FIG. 30 illustrates a select relationship screen embodiment. This screen lists all the relationships associated with the currently selected participant in the genogram. The user may be able to select table cells (that represent the relationship) for editing.

[00189] FIG. 31 illustrates a relationship reset screen embodiment. This screen allows the user to reset all the relationships for the currently active family. This is accessed by the 'Reset Relationships' button from the toolbar.

[00190] FIG. 32 illustrates a select household screen embodiment. This screen allows the user to delete all relationships in the current genomap. The Person In Relationship will also be deleted if they do not have any other relationships.

[00191] FIG. 33 illustrates an add new household screen

embodiment. This screen allows the user to select an already-added

household, which in turn launches the 'Edit Household Details' Screen. This select household screen is launched by selecting the 'Select Household' button from the toolbar.

[00192] FIG. 34 illustrates a select household members screen embodiment. This screen allows the user to select participants of the genogram as members of the household being added or edited. The above screens also show the view with 'traditional' icons and 'genogram' icons.

[00193] FIG. 35 illustrates an edit household details screen embodiment. This screen allows the user to edit a household in the genogram.

[00194] FIG. 36 illustrates a delete household confirmation screen embodiment. This screen adds a level of security from accidental deletion of a household.

[00195] FIG. 37 illustrates an electronic mail screen embodiment. These screens show the email function of the genomap application, in both 'traditional' icons as well as the 'genomap' icons. This function allows the user to send an image representation of the genomap main view.

[00196] FIG. 38 illustrates a print screen embodiment. This screen presents the user with a printer-friendly version of the genogram display. The above screens show the print view in both a 'traditional' icon set as well as the 'genogram' icons. In addition, there is a genogram legend included with every print to easily distinguish the information clearly.

[00197] FIG. 39 illustrates a data model of the embodiment. This screen shows a quickly accessible legend of what all icons and color codes mean within the genogram application. The above screens are shown for both 'traditional' icons and 'genogram' icons. This is accessed by the 'Legend' Button from the toolbar.

[00198] Entities

[00199] PersonDetails

[00200] This entity contains all the information related to a Person, from their profile to their image icon. When a person is added or changed in the 'Add Person' and 'Edit Person Details' screens, the details of that screen is added to this table.

[00201] PersonlnRelationship

[00202] This entity contains information about a person who is in a relationship. This information is used to properly display the person in the main genogram view.

[00203] Characteristics

[00204] This entity contains information about a person's

characteristics and person description. When a user selects characteristics from the 'Characteristic Picker' screen, that information is stored here. This information is also used to draw the characteristic icons on the person's image in the main genogram view.

[00205] Options

[00206] This entity simply stores the type of icons, either

Traditional' or 'Genogram', which is currently active in the main genogram view. The information is set by using the 'Icon Change' screen, and is used to display the icon motif in the main genogram view.

[00207] HouseholdDetails

[00208] This entity contains information related to a household. This information is stored or changed when a user accesses the 'Add New

Household' and 'Edit Household Details' screens.

[00209] FamilyDetails

[00210] This entity contains information related to a family. This information is stored or changed when a user accesses the 'Add New Family', 'Delete Family Confirmation Dialog', 'Reset Family Confirmation Dialog', and 'Edit Family Details' screens.

[00211] Relationshiplnfo

[00212] This entity contains information related to relationships. It contains info relating to who is in the relationship, what the relationship type is, as well as information required to draw the relationship in the main genogram view. This info is stored or changed when a user accesses the 'Edit Relationship Details', 'Relationship Reset Confirmation', and 'Delete

Relationship Confirmation' screens.

[00213] The previous description of the embodiments is provided to enable any person skilled in the art to practice the disclosure. The various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without the use of inventive faculty. Thus, the present disclosure is not intended to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

WHAT IS CLAIMED IS:

1. A method of tracking relationships comprising: prompting a user to input first person data; prompting the user to input second person data; prompting the user to input a relationship between the first person data and the second person data; genomapping the relationship between the first person data and the second person data with a processor; displaying the genomapping on a display.

2. The method of claim 1, wherein the relationship is a familial relationship.

3. The method of claim 2, wherein the familial relationship includes at least one of the following: adopted parent, biological parent, marriage relationship, common-law marriage relationship, child relationship, or parent relationship.

4. The method of claim 1, wherein the relationship is an abusive relationship.

5. The method of claim 4, wherein the abusive relationship includes at least one of the following: emotional abuse, hostile relationship, physical abuse relationship, or sexual abuse relationship.

6. An apparatus comprising: a user interface configured to prompt a user to input first person data, to prompt the user to input second person data, and to prompt the user to input a relationship between the first person data and the second person data; a processor configured to genomap the relationship between the first person data and the second person data; a display configured to visualize the genomapping.

7. The apparatus of claim 6, wherein the relationship is a familial relationship.

8. The apparatus of claim 7, wherein the familial relationship includes at least one of the following: adopted parent, biological parent, marriage relationship, common-law marriage relationship, child relationship, or parent relationship.

9. The apparatus of claim 6, wherein the relationship is an abusive relationship.

10. The apparatus of claim 9, wherein the abusive relationship includes at least one of the following: emotional abuse, hostile relationship, physical abuse relationship, or sexual abuse relationship.

1 1. A non-transitory computer readable medium encoded with data and instructions, when executed by a computing device the instructions causing the computing device to: prompt a user to input first person data; prompt the user to input second person data; prompt the user to input a relationship between the first person data and the second person data; genomap the relationship between the first person data and the second person data with a processor; visualize the genomap on a display.

12. The non-transitory computer readable medium of claim 1 1, wherein the relationship is a familial relationship.

13. The non-transitory computer readable medium of claim 12, wherein the familial relationship includes at least one of the following: adopted parent, biological parent, marriage relationship, common-law marriage relationship, child relationship, or parent relationship.

14. The non-transitory computer readable medium of claim 1 1, wherein the relationship is an abusive relationship.

15. The non-transitory computer readable medium of claim 14, wherein the abusive relationship includes at least one of the following:

emotional abuse, hostile relationship, physical abuse relationship, or sexual abuse relationship.