-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Representation of life status #7
Comments
@buske, I am not sure if it will be informative for you, but the Kids First Data Resource Center (KFDRC) created a custom profile called VitalStatus off of Observation (based on that Observation should record events at a point in time). Thus, we considered an inndividual's vital status as an observation event where Please see the followings:
|
Thank you, @liberaliscomputing. That is very helpful to see, and fits well with the structure proposed for eventually supporting Events. In terms of coding the life/vital status, SNOMED-CT isn't an open terminology, so I don't think we should recommend it's use for international standards. |
Re naming, here are some examples from established ontologies:
|
#6 introduces an
Individual.lifeStatus
property of typeConcept
, but there is no guidance as to the terminology.A. [Ideal] we would use an existing terminology with concepts that correspond to
alive
,deceased
, andunborn
B. use a string enum with the stated 3 values
C. expand the pedigree relationship ontology to include a branch with life statuses and add these three concepts
The text was updated successfully, but these errors were encountered: