Changes between Version 102 and Version 103 of BluePrintVITA


Ignore:
Timestamp:
11/29/10 13:38:28 (11 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintVITA

    v102 v103  
    11[[TOC]]
    2 = Blueprint: VITA Person Entity Model =
    3 
    4 '''Version 2.0''' - ''under construction''
    5 
    6 '''VITA''' is the proposed application design for '''storage, manipulation and communication of person-related information''' in S3 applications - it defines a set of data structures, interfaces and interoperability features to be implemented.
    7 == Overview ==
    8 
    9 VITA defines:
    10 
    11   - an extensible data model for tagging, tracking and tracing of person entities
    12   - a set of interfaces to request and manipulate person entity data
    13   - an XML-based data format to communicate person entity data
    14 
    15 == Ontology ==
     2= Blueprint: VITA =
     3
     4== Description ==
     5
     6'''VITA''' is an Eden application for '''storage, manipulation and communication of person-related information''' - and implements a set of data structures, functions, interfaces and interoperability features for this subject matter.
     7
     8'''Components:'''
     9
     10  * VITA Core
     11  * PR - Person Registry
     12  * PF - Person Finder Application (formerly Missing Persons Registry)
     13  * DVI - Application for Management of Dead Bodies and Disaster Victim Identification
     14
     15== Requirements ==
     16
     17=== Use-Cases ===
     18
     19'''Anybody'''
     20  - Report a fatality/find of a body
     21  - See a list of missing persons
     22  - Report sightings of missing persons
     23
     24'''The victim'''
     25  - Notify family members/friends about his/her whereabouts (and status)
     26  - Notify family members/friends about contact opportunities
     27
     28'''Relatives/friends of the victim'''
     29  - Find out the whereabouts/contact opportunities of a family member/friend
     30  - Report a family member/friend missing
     31  - Report a family member/friend found
     32  - Get notified when a missing family member/friend gets found
     33
     34'''Hospital Staff'''
     35  - Check-in a patient
     36  - Check-out a patient
     37  - See a list of current/former patients
     38  - Find out whether a patient is reported missing
     39  - Find out contact details of relatives/friends of a person
     40  - Register a fatality
     41  - Submit a body collection request
     42
     43'''Shelter Staff'''
     44  - Check-in a person
     45  - Check-out a person
     46  - See a list of current/former occupants
     47  - Find out whether a person is reported missing
     48  - Find out contact details of relatives/friends of a person
     49  - Register a fatality
     50  - Submit a body collection request
     51
     52'''Help Desk / Call center'''
     53  - Enter any reports/notifications/request on behalf of someone else
     54  - Retrieve information about whereabouts/contact opportunities on missing persons on behalf of someone else
     55
     56'''Body Recovery Team'''
     57  - Get notified about bodies to be recovered/collected
     58  - See a list of unrecovered/uncollected bodies in their area
     59  - See a map of unrecovered/uncollected bodies in their area
     60  - Manage/schedule recovery/collection requests
     61  - Confirm (report) the recovery/collection of a body (or the impossibility of recovery/collection)
     62
     63'''Person Search Team'''
     64  - Get a list of missing persons
     65  - Find out details for a missing person (missing reports, reported check-ins/check-outs/sightings, personal details, contact information, physical description)
     66  - Find out contact details of family members/friends
     67  - Find out contact details of reporters
     68  - Enter details for a missing person (including photographs)
     69  - Confirm reports of sightings
     70  - Report a person found
     71
     72'''Morgue Staff'''
     73  - Register a dead body
     74  - Register personal effects recovered/collected together with a body (including photographs)
     75  - Report physical details of a dead body (including photographs)
     76  - Report on storage/transfer of a body
     77  - Report on release/disposal of a body
     78  - Report storage/transfer/release/disposal of personal effects items
     79
     80'''Death Investigator'''
     81  - See a list of registered dead bodies
     82  - Compare details of a dead body with missing persons and find candidate matches
     83  - Establish the identity of a dead body
     84  - Find out contact details of relatives/friends
     85  - Confirm the identity of a dead body (declare a person deceased)
     86
     87== Design ==
     88
     89=== Ontology ===
    1690
    1791VITA defines four axes (aspects) for the construction of "Personal Data":
     
    28102  - [http://ontology.nursix.org/vita.owl OWL Source] ([http://ontology.nursix.org/vita.png Class Tree])
    29103
    30 === Entity ===
     104==== Entity ====
    31105
    32106The ''entity'' axis determines the entity type to which the data set relates (=ownership), which can be types of:
     
    38112  - Relationship
    39113
    40 === Distinction ===
     114==== Distinction ====
    41115
    42116The ''distinction'' axis describes any features which are used to distinguish particular person entities.
     
    48122Identities don't have to be unique across multiple domains. In case they are not, any communications of identities have to enclose a reference to the domain which administrates the particular identity (administrative domain).
    49123
    50 === Findings ===
     124==== Findings ====
    51125
    52126''Findings'' are all other features of the person entity which are to be communicated in this data set. These features can be assigned, observed or derived.
     
    54128  ''In the VITA context, photographs or other images are findings, not evidence.''
    55129
    56 === Evidence ===
     130==== Evidence ====
    57131
    58132''Evidence'' is any suitable means to describe the quality of data of the findings.
     
    60134  ''This always includes at least information on origin and time of the particular finding, but can also include references and links to sources, or information on methods of determination.''
    61135
    62 === Examples ===
     136==== Examples ====
    63137
    64138{{{
     
    96170  is a compliant set - it contains the "Entity" (pfif:person), "Distinction" (pfif:person_record_id, pfif:first_name, pfif:last_name), several "Findings" (pfif:sex, pfif:date_of_birth, pfif:age, pfif:photo_url) and plenty of "Evidence" (pfif:author_name, pfif:source_name, etc.).
    97171
    98 == Application Model ==
    99 
    100172=== Registries ===
    101173
     
    127199Data which only change upon administrative measures (e.g. names) do not need to be version-tracked.
    128200
    129 == Data Model ==
    130 
    131 ''under construction''
     201=== Data Model ===
     202
     203==== Overview ====
    132204
    133205[[Image(vita.png)]]
    134206
    135 === Undefined values ===
     207==== Undefined values ====
    136208
    137209Some (atomic) features in personal data sets are not applicable to all instances of the set (e.g. "Occupation" not applicable for infants), thus undefined values can be ambiguous here. For disambiguation, VITA implementations handle undefined values always as "not available", whereas "not applicable" must be defined explicitly and must not be the default value.
    138210
    139 === Roles ===
     211==== Roles ====
    140212
    141213Any person entity can be assigned to roles, which qualify the entity for inclusion into certain processes. One and the same instance of the entity can be assigned to multiple roles at the same time.
     
    143215Within a role, the entity instance can be assigned to a status, where the status values must be discrete, unambiguous and consistent. There can only be one status per instance and role at a time. VITA implementations should keep a tally of all status transitions of an entity instance in such way that it is possible to reconstruct the role and status of the entity instance for any point or interval of time.
    144216
    145 === Presence ===
     217==== Presence ====
    146218
    147219Presence means the fact, that an instance of a person entity is physically there at a particular '''location''' at a particular '''time'''. This abstract construction covers even cases of explicit absence, i.e. when the entity is ''not'' present at ''that'' location at ''that'' time.
     
    166238  ||Lost||no longer at this location, but destroyed/disposed/deceased here||
    167239
    168 === Names ===
     240==== Names ====
    169241
    170242Names are used to identify persons in human communication. However, names of persons do not have to be unique nor do they have to be exact. The following name fields are mandatory to exist in individual person records:
     
    184256 * An application may define additional name fields to represent e.g. titles, nicknames or pseudonyms, however, these additional fields must not be used to repeat or replace any of the mandatory fields.
    185257
    186 == Motivation ==
    187 
    188 == Rationale ==
    189 
    190258== Implementations ==
    191259