Class DeathRecord
Class DeathRecord
models a FHIR Standard Death Record (SDR).
For consuming a FHIR SDR (in either XML or JSON format), there is a constructor that
takes a string, which will parse the given FHIR SDR and build a new DeathRecord
that
represents it. You can then use the various property getters to infer details about the
record.
For producing a new FHIR SDR, there is a default no-param constructor that creates the bare
bones necessary for a new record. You can then use the various property setters to
populate details of the record. All DeathRecord
s can be converted to FHIR XML or JSON
suitable for transmission, by making use of the ToXML()
and ToJSON()
methods.
Inheritance
Inherited Members
Namespace: FhirDeathRecord
Assembly: cs.temp.dll.dll
Syntax
public class DeathRecord
Constructors
DeathRecord()
Default constructor that creates a new, empty FHIR SDR.
Declaration
public DeathRecord()
DeathRecord(String, Boolean)
Constructor that takes a string that represents a FHIR SDR in either XML or JSON format.
Declaration
public DeathRecord(string record, bool permissive = false)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | record | represents a FHIR SDR in either XML or JSON format. |
| System.Boolean | permissive | if the parser should be permissive when parsing the given string |
Exceptions
| Type | Condition |
|---|---|
| System.ArgumentException | Record is neither valid XML nor JSON. |
Properties
ActualOrPresumedDateOfDeath
Actual or presumed date of death. Corresponds to item 29 of the U.S. Standard Certificate of Death.
Declaration
[Property("Actual Or Presumed Date Of Death", Property.Types.StringDateTime, "Medical", "Actual or presumed date of death.", true, 43)]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='81956-5')", "")]
public string ActualOrPresumedDateOfDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | Actual or presumed date of death |
Examples
// Setter:
ExampleDeathRecord.ActualOrPresumedDateOfDeath = "2018-04-24T00:00:00+00:00";
// Getter:
Console.WriteLine($"Actual or presumed date of death: {ExampleDeathRecord.ActualOrPresumedDateOfDeath}");
Age
The decedent’s age in years at last birthday. Corresponds to item 4a of the U.S. Standard Certificate of Death.
Declaration
[Property("Age", Property.Types.String, "Demographics", "The decedent’s age in years at last birthday.", true, 19)]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-Age-extension')", "")]
public string Age { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | The decedent’s age in years at last birthday. |
Examples
// Setter:
ExampleDeathRecord.Age = "100";
// Getter:
Console.WriteLine($"Age in years at last birthday.: {ExampleDeathRecord.Age}");
AutopsyPerformed
Whether an autopsy was performed (true) or not (false). Corresponds to item 33 of the U.S. Standard Certificate of Death.
Declaration
[Property("Autopsy Performed", Property.Types.Bool, "Medical", "Whether an autopsy was performed or not.", true, 39)]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='85699-7')", "")]
public bool AutopsyPerformed { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean | Whether an autopsy was performed (true) or not (false) |
Examples
// Setter:
ExampleDeathRecord.AutopsyPerformed = true;
// Getter:
Console.WriteLine($"Was autopsy was performed?: {ExampleDeathRecord.AutopsyPerformed}");
AutopsyResultsAvailable
Were autopsy findings available to complete the cause of death? Corresponds to item 34 of the U.S. Standard Certificate of Death.
Declaration
[Property("Autopsy Results Available", Property.Types.Bool, "Medical", "Were autopsy findings available to complete the cause of death?", true, 10)]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='69436-4')", "")]
public bool AutopsyResultsAvailable { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean | Were autopsy findings available to complete the cause of death? |
Examples
// Setter:
ExampleDeathRecord.AutopsyResultsAvailable = true;
// Getter:
Console.WriteLine($"Were autopsy findings available to complete the cause of death?: {ExampleDeathRecord.AutopsyResultsAvailable}");
BirthSex
Decedent's Birth Sex.
Declaration
[Property("Birth Sex", Property.Types.Dictionary, "Demographics", "Decedent's Birth Sex.", true, 9)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://hl7.org/fhir/us/core/StructureDefinition/us-core-birthsex')", "")]
public Dictionary<string, string> BirthSex { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | the decedent's birth sex |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "M");
code.Add("system", "http://hl7.org/fhir/us/core/ValueSet/us-core-birthsex");
code.Add("display", "Male");
ExampleDeathRecord.BirthSex = code;
// Getter:
foreach(var pair in ExampleDeathRecord.BirthSex)
{
Console.WriteLine($"\tAddress key: {pair.Key}: value: {pair.Value}");
};
CausesOfDeath
Conditions that resulted in the cause of death. Corresponds to part 1 of item 32 of the U.S. Standard Certificate of Death.
Declaration
[Property("Causes Of Death", Property.Types.TupleCOD, "Medical", "Conditions that resulted in the cause of death.", true, 37)]
[FHIRPath("Bundle.entry.resource.where($this is Condition).where(onset.empty().not())", "")]
public Tuple<string, string, Dictionary<string, string>>[] CausesOfDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Tuple<System.String, System.String, System.Collections.Generic.Dictionary<System.String, System.String>>[] | Conditions that resulted in the underlying cause of death. An array of tuples (in the order they would appear on a death certificate, from top to bottom), each containing the cause of death literal (Tuple "Item1") the approximate onset to death (Tuple "Item2"), and an (optional) Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Tuple<string, string, Dictionary<string, string>>[] causes =
{
Tuple.Create("Example Immediate COD", "minutes", new Dictionary<string, string>(){ {"code", "1234"}, {"system", "example"} }),
Tuple.Create("Example Underlying COD 1", "2 hours", new Dictionary<string, string>()),
Tuple.Create("Example Underlying COD 2", "6 months", new Dictionary<string, string>()),
Tuple.Create("Example Underlying COD 3", "15 years", new Dictionary<string, string>())
};
ExampleDeathRecord.CausesOfDeath = causes;
// Getter:
Tuple<string, string>[] causes = ExampleDeathRecord.CausesOfDeath;
foreach (var cause in causes)
{
Console.WriteLine($"Cause: {cause.Item1}, Onset: {cause.Item2}, Code: {cause.Item3}");
}
CertifierAddress
Address of certifier.
Declaration
[Property("Certifier's Address", Property.Types.Dictionary, "Medical", "Address of certifier.", true, 34)]
[PropertyParam("certifierAddressLine1", "certifier address, line one")]
[PropertyParam("certifierAddressLine2", "certifier address, line two")]
[PropertyParam("certifierAddressCity", "certifier address, city")]
[PropertyParam("certifierAddressCounty", "certifier address, county")]
[PropertyParam("certifierAddressState", "certifier address, state")]
[PropertyParam("certifierAddressZip", "certifier address, zip")]
[PropertyParam("certifierAddressCountry", "certifier address, country")]
[FHIRPath("Bundle.entry.resource.where($this is Practitioner)", "address")]
public Dictionary<string, string> CertifierAddress { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | the certifier's address |
Examples
// Setter:
Dictionary<string, string> address = new Dictionary<string, string>();
address.Add("certifierAddressLine1", "123 Test Street");
address.Add("certifierAddressLine2", "Unit 3");
address.Add("certifierAddressCity", "Boston");
address.Add("certifierAddressCounty", "Suffolk");
address.Add("certifierAddressState", "Massachusetts");
address.Add("certifierAddressZip", "12345");
ExampleDeathRecord.CertifierAddress = address;
// Getter:
foreach(var pair in ExampleDeathRecord.CertifierAddress)
{
Console.WriteLine($"\tCertifierAddress key: {pair.Key}: value: {pair.Value}");
};
CertifierFamilyName
Family name of certifier.
Declaration
[Property("Certifier's Family Name", Property.Types.String, "Medical", "Family name of certifier.", true, 32)]
[FHIRPath("Bundle.entry.resource.where($this is Practitioner)", "name")]
public string CertifierFamilyName { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the certifier's family name (i.e. last name) |
Examples
// Setter:
ExampleDeathRecord.CertifierFamilyName = "Last";
// Getter:
Console.WriteLine($"Certifier's Last Name: {string.Join(", ", ExampleDeathRecord.CertifierFamilyName)}");
CertifierGivenNames
Given name(s) of certifier.
Declaration
[Property("Certifier's Given Names", Property.Types.StringArr, "Medical", "Given name(s) of certifier.", true, 31)]
[FHIRPath("Bundle.entry.resource.where($this is Practitioner)", "name")]
public string[] CertifierGivenNames { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String[] | the certifier's name (first, middle, etc.) |
Examples
// Setter:
string[] names = {"Doctor", "Middle"};
ExampleDeathRecord.CertifierGivenNames = names;
// Getter:
Console.WriteLine($"Certifier Given Name(s): {string.Join(", ", ExampleDeathRecord.CertifierGivenNames)}");
CertifierQualification
Certifier Qualification.
Declaration
[Property("Certifier Qualification", Property.Types.Dictionary, "Medical", "Certifier's Qualification.", true, 36)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Practitioner)", "qualification")]
public Dictionary<string, string> CertifierQualification { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | the certifier qualification |
Examples
// Setter:
Dictionary<string, string> qualification = new Dictionary<string, string>();
code.Add("code", "MD");
code.Add("system", "http://hl7.org/fhir/v2/0360/2.7");
code.Add("display", "Doctor of Medicine");
ExampleDeathRecord.CertifierQualification = qualification;
// Getter:
Console.WriteLine($"\tCertifier Qualification: {ExampleDeathRecord.CertifierQualification['display']}");
CertifierSuffix
Certifier's Suffix.
Declaration
[Property("Certifier's Suffix", Property.Types.String, "Medical", "Certifier's Suffix.", true, 33)]
[FHIRPath("Bundle.entry.resource.where($this is Practitioner)", "name")]
public string CertifierSuffix { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the certifier's suffix |
Examples
// Setter:
ExampleDeathRecord.CertifierSuffix = "Jr.";
// Getter:
Console.WriteLine($"Certifier Suffix: {ExampleDeathRecord.CertifierSuffix}");
CertifierType
Certifier Type.
Declaration
[Property("Certifier Type", Property.Types.Dictionary, "Medical", "Certifier Type.", true, 35)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Practitioner).extension.where(url = 'http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-deathRecord-CertifierType-extension')", "")]
public Dictionary<string, string> CertifierType { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | the certifier type |
Examples
// Setter:
Dictionary<string, string> type = new Dictionary<string, string>();
code.Add("code", "434651000124107");
code.Add("display", "Physician (Pronouncer and Certifier)");
ExampleDeathRecord.CertifierType = type;
// Getter:
Console.WriteLine($"\tCertifier Type: {ExampleDeathRecord.CertifierType['display']}");
COD1A
An alias for the CausesOfDeath
property - Cause of Death Part I, Line a.
Declaration
[Property("COD1A", Property.Types.String, "Medical", "Cause of Death Part I, Line a.", false, 1)]
public string COD1A { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
COD1B
An alias for the CausesOfDeath
property - Cause of Death Part I, Line b.
Declaration
[Property("COD1B", Property.Types.String, "Medical", "Cause of Death Part I, Line b.", false, 1)]
public string COD1B { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
COD1C
An alias for the CausesOfDeath
property - Cause of Death Part I, Line c.
Declaration
[Property("COD1C", Property.Types.String, "Medical", "Cause of Death Part I, Line c.", false, 1)]
public string COD1C { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
COD1D
An alias for the CausesOfDeath
property - Cause of Death Part I, Line d.
Declaration
[Property("COD1D", Property.Types.String, "Medical", "Cause of Death Part I, Line d.", false, 1)]
public string COD1D { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
CODE1A
An alias for the CausesOfDeath
property - Cause of Death Part I Code, Line a.
Declaration
[Property("CODE1A", Property.Types.String, "Medical", "Cause of Death Part I Code, Line a.", false, 1)]
public Dictionary<string, string> CODE1A { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> |
CODE1B
An alias for the CausesOfDeath
property - Cause of Death Part I Code, Line b.
Declaration
[Property("CODE1B", Property.Types.String, "Medical", "Cause of Death Part I Code, Line b.", false, 1)]
public Dictionary<string, string> CODE1B { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> |
CODE1C
An alias for the CausesOfDeath
property - Cause of Death Part I Code, Line c.
Declaration
[Property("CODE1C", Property.Types.String, "Medical", "Cause of Death Part I Code, Line c.", false, 1)]
public Dictionary<string, string> CODE1C { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> |
CODE1D
An alias for the CausesOfDeath
property - Cause of Death Part I Code, Line d.
Declaration
[Property("CODE1D", Property.Types.String, "Medical", "Cause of Death Part I Code, Line d.", false, 1)]
public Dictionary<string, string> CODE1D { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> |
ContributingConditions
A significant condition that contributed to death but did not result in the underlying cause captured by a CauseOfDeathCondition. Corresponds to part 2 of item 32 of the U.S. Standard Certificate of Death.
Declaration
[Property("Contributing Conditions", Property.Types.String, "Medical", "Contributing Conditions", true, 38)]
[FHIRPath("Bundle.entry.resource.where($this is Condition).where(onset.empty())", "")]
public string ContributingConditions { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | A significant condition that contributed to death but did not result in the underlying cause captured by a CauseOfDeathCondition. |
Examples
// Setter:
ExampleDeathRecord.ContributingConditions = "Example Contributing Condition";
// Getter:
Console.WriteLine($"Cause: {ExampleDeathRecord.ContributingConditions}");
DateOfBirth
Decedent's Date of Birth.
Declaration
[Property("Date Of Birth", Property.Types.StringDateTime, "Demographics", "Decedent's Date of Birth.", true, 10)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "birthDate")]
public string DateOfBirth { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's date of birth |
Examples
// Setter:
ExampleDeathRecord.DateOfBirth = "1970-04-24";
// Getter:
Console.WriteLine($"Decedent Suffix: {ExampleDeathRecord.DateOfBirth}");
DateOfDeath
Decedent's Date and Time of Death.
Declaration
[Property("Date Of Death", Property.Types.StringDateTime, "Demographics", "Decedent's Date and Time of Death.", true, 9)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "deceasedDateTime")]
public string DateOfDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's date and time of death |
Examples
// Setter:
ExampleDeathRecord.DateOfDeath = "1970-04-24";
// Getter:
Console.WriteLine($"Decedent Suffix: {ExampleDeathRecord.DateOfDeath}");
DateOfRegistration
Death Record Registration Date.
Declaration
[Property("Date Of Registration", Property.Types.StringDateTime, "Record Details", "Death Record Registration Date.", true, 2)]
[FHIRPath("Bundle.entry.resource.where($this is Composition)", "date")]
public string DateOfRegistration { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | when the record was registered |
Examples
// Setter:
ExampleDeathRecord.DateOfRegistration = "2018-07-11";
// Getter:
Console.WriteLine($"Record was registered on: {ExampleDeathRecord.DateOfRegistration}");
DatePronouncedDead
Date pronounced dead. Corresponds to items 24 and 25 of the U.S. Standard Certificate of Death.
Declaration
[Property("Date Pronounced Dead", Property.Types.StringDateTime, "Medical", "Date pronounced dead.", true, 44)]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='80616-6')", "")]
public string DatePronouncedDead { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | Date pronounced dead |
Examples
// Setter:
ExampleDeathRecord.DatePronouncedDead = "2018-04-24T00:00:00+00:00";
// Getter:
Console.WriteLine($"Date pronounced dead: {ExampleDeathRecord.DatePronouncedDead}");
DeathFromTransportInjury
Injury leading to death associated with transportation event. Corresponds to item 44 of the U.S. Standard Certificate of Death.
Declaration
[Property("Death From Transport Injury", Property.Types.Dictionary, "Medical", "Injury leading to death associated with transportation event.", true, 46)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='69448-9')", "")]
public Dictionary<string, string> DeathFromTransportInjury { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Injury leading to death associated with transportation event. A Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "236320001");
code.Add("system", "http://github.com/nightingaleproject/fhirDeathRecord/sdr/causeOfDeath/vs/TransportRelationshipsVS");
code.Add("display", "Vehicle driver");
ExampleDeathRecord.DeathFromTransportInjury = code;
// Getter:
Console.WriteLine($"Injury leading to death associated with transportation event: {ExampleDeathRecord.DeathFromTransportInjury["display"]}");
DeathFromWorkInjury
Did death result from injury at work? Corresponds to item 41 of the U.S. Standard Certificate of Death.
Declaration
[Property("Death From Work Injury", Property.Types.Bool, "Medical", "Did death result from injury at work?", true, 45)]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='69444-8')", "")]
public bool DeathFromWorkInjury { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean | Did death result from injury at work? |
Examples
// Setter:
ExampleDeathRecord.DeathFromWorkInjury = true;
// Getter:
Console.WriteLine($"Did death result from injury at work?: {ExampleDeathRecord.DeathFromWorkInjury}");
DetailsOfInjury
Injury incident description.
Declaration
[Property("Details Of Injury", Property.Types.Dictionary, "Medical", "Injury incident description.", true, 49)]
[PropertyParam("detailsOfInjuryPlaceDescription", "description of the place of injury")]
[PropertyParam("detailsOfInjuryEffectiveDateTime", "effective date and time of injury")]
[PropertyParam("detailsOfInjuryDescription", "description of the injury")]
[PropertyParam("detailsOfInjuryLine1", "location of injury, line one")]
[PropertyParam("detailsOfInjuryLine2", "location of injury, line two")]
[PropertyParam("detailsOfInjuryCity", "location of injury, city")]
[PropertyParam("detailsOfInjuryCounty", "location of injury, county")]
[PropertyParam("detailsOfInjuryState", "location of injury, state")]
[PropertyParam("detailsOfInjuryZip", "location of injury, zip")]
[PropertyParam("detailsOfInjuryCountry", "location of injury, country")]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='11374-6')", "")]
public Dictionary<string, string> DetailsOfInjury { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Injury incident description. A Dictionary representing a description of an injury incident, containing the following key/value pairs: "detailsOfInjuryPlaceDescription" - description of the place of injury, e.g. decedent’s home, restaurant, wooded area "detailsOfInjuryEffectiveDateTime" - effective date and time of injury "detailsOfInjuryDescription" - description of the injury "detailsOfInjuryLine1" - location of injury, line one "detailsOfInjuryLine2" - location of injury, line two "detailsOfInjuryCity" - location of injury, city "detailsOfInjuryCounty" - location of injury, county "detailsOfInjuryState" - location of injury, state "detailsOfInjuryZip" - location of injury, zip "detailsOfInjuryCountry" - location of injury, country |
Examples
// Setter:
Dictionary<string, string> detailsOfInjury = new Dictionary<string, string>();
detailsOfInjury.Add("detailsOfInjuryPlaceDescription", "Home");
detailsOfInjury.Add("detailsOfInjuryEffectiveDateTime", "2018-04-19T15:43:00+00:00");
detailsOfInjury.Add("detailsOfInjuryDescription", "Example details of injury");
detailsOfInjury.Add("detailsOfInjuryLine1", "7 Example Street");
detailsOfInjury.Add("detailsOfInjuryLine2", "Unit 1234");
detailsOfInjury.Add("detailsOfInjuryCity", "Bedford");
detailsOfInjury.Add("detailsOfInjuryCounty", "Middlesex");
detailsOfInjury.Add("detailsOfInjuryState", "Massachusetts");
detailsOfInjury.Add("detailsOfInjuryZip", "01730");
detailsOfInjury.Add("detailsOfInjuryCountry", "United States");
ExampleDeathRecord.DetailsOfInjury = detailsOfInjury;
// Getter:
string state = ExampleDeathRecord.DetailsOfInjury["detailsOfInjuryState"];
Console.WriteLine($"State where injury occurred: {state}");
Disposition
Disposition of the decedent’s body. Corresponds to items 18, 19, 20, 21, 22 and 23 of the U.S. Standard Certificate of Death.
Declaration
[Property("Disposition", Property.Types.Dictionary, "Disposition", "Disposition of the decedent’s body.", true, 25)]
[PropertyParam("dispositionTypeCode", "the code describing the method of disposition of the decedent’s remains")]
[PropertyParam("dispositionTypeSystem", "the code system describing the method of disposition of the decedent’s remains")]
[PropertyParam("dispositionTypeDisplay", "the human readable code display text that describes the method of disposition of the decedent’s remains")]
[PropertyParam("dispositionPlaceLine1", "disposition place address, line one")]
[PropertyParam("dispositionPlaceLine2", "disposition place address, line two")]
[PropertyParam("dispositionPlaceCity", "disposition place address, city")]
[PropertyParam("dispositionPlaceCounty", "disposition place address, county")]
[PropertyParam("dispositionPlaceState", "disposition place address, state")]
[PropertyParam("dispositionPlaceZip", "disposition place address, zip")]
[PropertyParam("dispositionPlaceCountry", "disposition place address, country")]
[PropertyParam("funeralFacilityName", "the name of a funeral facility or institution")]
[PropertyParam("dispositionPlaceLine1", "funeral facility address, line one")]
[PropertyParam("dispositionPlaceLine2", "funeral facility address, line two")]
[PropertyParam("dispositionPlaceCity", "funeral facility address, city")]
[PropertyParam("dispositionPlaceCounty", "funeral facility address, county")]
[PropertyParam("dispositionPlaceState", "funeral facility address, state")]
[PropertyParam("dispositionPlaceZip", "funeral facility address, zip")]
[PropertyParam("dispositionPlaceCountry", "funeral facility address, country")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-Disposition-extension')", "")]
public Dictionary<string, string> Disposition { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Disposition of the decedent’s body. A Dictionary representing the disposition, containing the following key/value pairs: "dispositionTypeCode" - the code describing the method of disposition of the decedent’s remains "dispositionTypeSystem" - the code system describing the method of disposition of the decedent’s remains "dispositionTypeDisplay" - the human readable code display text that describes the method of disposition of the decedent’s remains "dispositionPlaceName" - the name of the disposition place "dispositionPlaceLine1" - disposition place address, line one "dispositionPlaceLine2" - disposition place address, line two "dispositionPlaceCity" - disposition place address, city "dispositionPlaceCounty" - disposition place address, county "dispositionPlaceState" - disposition place address, state "dispositionPlaceZip" - disposition place address, zip "dispositionPlaceCountry" - disposition place address, country "funeralFacilityName" - the name of a funeral facility or institution "funeralFacilityLine1" - funeral facility address, line one "funeralFacilityLine2" - funeral facility address, line two "funeralFacilityCity" - funeral facility address, city "funeralFacilityCounty" - funeral facility address, county "funeralFacilityState" - funeral facility address, state "funeralFacilityZip" - funeral facility address, zip "funeralFacilityCountry" - funeral facility address, country |
Examples
// Setter:
Dictionary<string, string> disposition = new Dictionary<string, string>();
disposition.Add("dispositionTypeCode", "449971000124106");
disposition.Add("dispositionTypeSystem", "http://snomed.info/sct");
disposition.Add("dispositionTypeDisplay", "Burial");
disposition.Add("dispositionPlaceName", "Example disposition place name");
disposition.Add("dispositionPlaceLine1", "100 Example Street");
disposition.Add("dispositionPlaceLine2", "Line 2");
disposition.Add("dispositionPlaceCity", "Bedford");
disposition.Add("dispositionPlaceCounty", "Middlesex");
disposition.Add("dispositionPlaceState", "Massachusetts");
disposition.Add("dispositionPlaceZip", "01730");
disposition.Add("dispositionPlaceCountry", "United States");
disposition.Add("funeralFacilityName", "Example funeral facility name");
disposition.Add("funeralFacilityLine1", "50 Example Street");
disposition.Add("funeralFacilityLine2", "Line 2");
disposition.Add("funeralFacilityCity", "Bedford");
disposition.Add("funeralFacilityCounty", "Middlesex");
disposition.Add("funeralFacilityState", "Massachusetts");
disposition.Add("funeralFacilityZip", "01730");
disposition.Add("funeralFacilityCountry", "United States");
ExampleDeathRecord.Disposition = disposition;
// Getter:
Console.WriteLine($"Funeral Facility name: {ExampleDeathRecord.Disposition["funeralFacilityName"]}");
Education
Decedent’s level of education. Corresponds to item 51 of the U.S. Standard Certificate of Death.
Declaration
[Property("Education", Property.Types.Dictionary, "Demographics", "Decedent’s level of education.", true, 18)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-Education-extension')", "")]
public Dictionary<string, string> Education { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Decedent’s level of education. A Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "PHC1453");
code.Add("system", "http://github.com/nightingaleproject/fhirDeathRecord/sdr/decedent/cs/EducationCS ");
code.Add("display", "Bachelor's Degree");
ExampleDeathRecord.MaritalStatus = code;
// Getter:
Console.WriteLine($"Degree: {ExampleDeathRecord.Education["display"]}");
Ethnicity
Decedent's Ethnicity.
Declaration
[Property("Ethnicity", Property.Types.TupleArr, "Demographics", "Decedent's Ethnicity.", true, 14)]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity')", "")]
public Tuple<string, string>[] Ethnicity { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Tuple<System.String, System.String>[] | the decedent's ethnicity |
Examples
// Setter:
Tuple<string, string>[] ethnicity = { Tuple.Create("Non Hispanic or Latino", "2186-5"), Tuple.Create("Salvadoran", "2161-8") };
ExampleDeathRecord.Ethnicity = ethnicity;
// Getter:
foreach(var pair in deathRecord.Ethnicity)
{
Console.WriteLine($"\tEthnicity text: {pair.Key}: code: {pair.Value}");
};
FamilyName
Decedent's Family Name.
Declaration
[Property("Family Name", Property.Types.String, "Demographics", "Decedent's Family Name.", true, 4)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "name")]
public string FamilyName { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's family name (i.e. last name) |
Examples
// Setter:
ExampleDeathRecord.FamilyName = "Last";
// Getter:
Console.WriteLine($"Decedent's Last Name: {ExampleDeathRecord.FamilyName}");
FatherFamilyName
Decedent's Father's Family Name.
Declaration
[Property("Father's Family Name", Property.Types.String, "Demographics", "Decedent's Father's Family Name.", true, 7)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "contact")]
public string FatherFamilyName { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's father's family name (i.e. last name) |
Examples
// Setter:
ExampleDeathRecord.FatherFamilyName = "Last";
// Getter:
Console.WriteLine($"Decedent's Father's Last Name: {ExampleDeathRecord.FatherFamilyName}");
Gender
Decedent's Gender.
Declaration
[Property("Gender", Property.Types.String, "Demographics", "Decedent's Gender.", true, 8)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "gender")]
public string Gender { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's gender |
Examples
// Setter:
ExampleDeathRecord.Gender = "female";
// Getter:
Console.WriteLine($"Decedent Suffix: {ExampleDeathRecord.Gender}");
GivenNames
Decedent's Given Name(s). Middle name should be the last entry.
Declaration
[Property("Given Names", Property.Types.StringArr, "Demographics", "Decedent's Given Name(s).", true, 3)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "name")]
public string[] GivenNames { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String[] | the decedent's name (first, etc., middle) |
Examples
// Setter:
string[] names = {"Example", "Something", "Middle"};
ExampleDeathRecord.GivenNames = names;
// Getter:
Console.WriteLine($"Decedent Given Name(s): {string.Join(", ", ExampleDeathRecord.GivenNames)}");
Id
Death Record ID.
Declaration
[Property("Id", Property.Types.String, "Record Details", "The record ID.", true, 1)]
[FHIRPath("Bundle", "id")]
public string Id { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the record identification |
Examples
// Setter:
ExampleDeathRecord.Id = "42";
// Getter:
Console.WriteLine($"Record identification: {ExampleDeathRecord.Id}");
INTERVAL1A
An alias for the CausesOfDeath
property - Cause of Death Part I Interval, Line a.
Declaration
[Property("INTERVAL1A", Property.Types.String, "Medical", "Cause of Death Part I Interval, Line a.", false, 1)]
public string INTERVAL1A { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
INTERVAL1B
An alias for the CausesOfDeath
property - Cause of Death Part I Interval, Line b.
Declaration
[Property("INTERVAL1B", Property.Types.String, "Medical", "Cause of Death Part I Interval, Line b.", false, 1)]
public string INTERVAL1B { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
INTERVAL1C
An alias for the CausesOfDeath
property - Cause of Death Part I Interval, Line c.
Declaration
[Property("INTERVAL1C", Property.Types.String, "Medical", "Cause of Death Part I Interval, Line c.", false, 1)]
public string INTERVAL1C { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
INTERVAL1D
An alias for the CausesOfDeath
property - Cause of Death Part I Interval, Line d.
Declaration
[Property("INTERVAL1D", Property.Types.String, "Medical", "Cause of Death Part I Interval, Line d.", false, 1)]
public string INTERVAL1D { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String |
MaidenName
Decedent's Maiden Name.
Declaration
[Property("Maiden Name", Property.Types.String, "Demographics", "Decedent's Maiden Name.", true, 6)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "name")]
public string MaidenName { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's maiden name (i.e. last name before marriage) |
Examples
// Setter:
ExampleDeathRecord.MaidenName = "Last";
// Getter:
Console.WriteLine($"Decedent's Maiden Name: {ExampleDeathRecord.MaidenName}");
MannerOfDeath
The manner of the decendent's demise. Corresponds to item 37 of the U.S. Standard Certificate of Death.
Declaration
[Property("Manner Of Death", Property.Types.Dictionary, "Medical", "The manner of the decendent's demise.", true, 41)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='69449-7')", "")]
public Dictionary<string, string> MannerOfDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | The manner of the decendent's demise. A Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "7878000");
code.Add("system", "http://github.com/nightingaleproject/fhirDeathRecord/sdr/causeOfDeath/vs/MannerOfDeathVS");
code.Add("display", "Accident");
ExampleDeathRecord.MannerOfDeath = code;
// Getter:
Console.WriteLine($"Manner of the decendents demise: {ExampleDeathRecord.MannerOfDeath["display"]}");
MaritalStatus
The marital status of the decedent at the time of death. Corresponds to item 9 of the U.S. Standard Certificate of Death.
Declaration
[Property("Marital Status", Property.Types.Dictionary, "Demographics", "Decedent's Marital Status at the time of death.", true, 17)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-MaritalStatusAtDeath-extension')", "")]
public Dictionary<string, string> MaritalStatus { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | The marital status of the decedent at the time of death. A Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "S");
code.Add("system", "http://hl7.org/fhir/v3/MaritalStatus");
code.Add("display", "Never Married");
ExampleDeathRecord.MaritalStatus = code;
// Getter:
Console.WriteLine($"Marital status: {ExampleDeathRecord.MaritalStatus["display"]}");
MedicalExaminerContacted
Whether a medical examiner or coroner was contacted. Corresponds to item 31 of the U.S. Standard Certificate of Death.
Declaration
[Property("Medical Examiner Contacted", Property.Types.Bool, "Medical", "Whether a medical examiner or coroner was contacted.", true, 47)]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='74497-9')", "")]
public bool MedicalExaminerContacted { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean | Whether a medical examiner or coroner was contacted |
Examples
// Setter:
ExampleDeathRecord.MedicalExaminerContacted = true;
// Getter:
Console.WriteLine($"Medical examiner or coroner was contacted?: {ExampleDeathRecord.MedicalExaminerContacted}");
Occupation
Decedent’s usual occupation and industry. Corresponds to items 54 and 55 of the U.S. Standard Certificate of Death.
Declaration
[Property("Occupation", Property.Types.Dictionary, "Demographics", "Decedent’s usual occupation and industry.", true, 21)]
[PropertyParam("jobDescription", "Type of work done during most of decedent’s working life.")]
[PropertyParam("industryDescription", "Kind of industry or business in which the decedent worked.")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-Occupation-extension')", "")]
public Dictionary<string, string> Occupation { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Decedent’s usual occupation and industry. "jobDescription" - Type of work done during most of decedent’s working life. Corresponds to item 54 of the U.S. Standard Certificate of Death. "industryDescription" - Kind of industry or business in which the decedent worked. Corresponds to item 55 of the U.S. Standard Certificate of Death. |
Examples
// Setter:
Dictionary<string, string> occupation = new Dictionary<string, string>();
occupation.Add("jobDescription", "Example occupation");
occupation.Add("industryDescription", "Example industry");
SetterDeathRecord.Occupation = occupation;
// Getter:
Console.WriteLine($"Job Description: {ExampleDeathRecord.Occupation["jobDescription"]}");
PlaceOfBirth
Decedent's Place Of Birth.
Declaration
[Property("Place Of Birth", Property.Types.Dictionary, "Demographics", "Decedent's Place Of Birth.", true, 15)]
[PropertyParam("placeOfBirthLine1", "location of birth, line one")]
[PropertyParam("placeOfBirthLine2", "location of birth, line two")]
[PropertyParam("placeOfBirthCity", "location of birth, city")]
[PropertyParam("placeOfBirthCounty", "location of birth, county")]
[PropertyParam("placeOfBirthState", "location of birth, state")]
[PropertyParam("placeOfBirthZip", "location of birth, zip")]
[PropertyParam("placeOfBirthCountry", "location of birth, country")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-Birthplace-extension')", "")]
public Dictionary<string, string> PlaceOfBirth { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Decedent's Place Of Birth. A Dictionary representing a place of birth address, containing the following key/value pairs: "placeOfBirthLine1" - location of birth, line one "placeOfBirthLine2" - location of birth, line two "placeOfBirthCity" - location of birth, city "placeOfBirthCounty" - location of birth, county "placeOfBirthState" - location of birth, state "placeOfBirthZip" - location of birth, zip "placeOfBirthCountry" - location of birth, country |
Examples
// Setter:
Dictionary<string, string> placeOfBirth = new Dictionary<string, string>();
placeOfBirth.Add("placeOfBirthLine1", "9 Example Street");
placeOfBirth.Add("placeOfBirthLine2", "Line 2");
placeOfBirth.Add("placeOfBirthCity", "Bedford");
placeOfBirth.Add("placeOfBirthCounty", "Middlesex");
placeOfBirth.Add("placeOfBirthState", "Massachusetts");
placeOfBirth.Add("placeOfBirthZip", "01730");
placeOfBirth.Add("placeOfBirthCountry", "United States");
SetterDeathRecord.PlaceOfBirth = placeOfBirth;
// Getter:
string state = ExampleDeathRecord.PlaceOfBirth["placeOfBirthState"];
Console.WriteLine($"State where decedent was born: {state}");
PlaceOfDeath
Decedent's Place Of Death.
Declaration
[Property("Place Of Death", Property.Types.Dictionary, "Demographics", "Decedent's Place Of Death.", true, 16)]
[PropertyParam("placeOfDeathTypeCode", "place of death type, code")]
[PropertyParam("placeOfDeathTypeSystem", "place of death type, code system")]
[PropertyParam("placeOfDeathTypeDisplay", "place of death type, code display")]
[PropertyParam("placeOfDeathFacilityName", "place of death facility name")]
[PropertyParam("placeOfDeathLine1", "location of death, line one")]
[PropertyParam("placeOfDeathLine2", "location of death, line two")]
[PropertyParam("placeOfDeathCity", "location of death, city")]
[PropertyParam("placeOfDeathCounty", "location of death, county")]
[PropertyParam("placeOfDeathState", "location of death, state")]
[PropertyParam("placeOfDeathZip", "location of death, zip")]
[PropertyParam("placeOfDeathCountry", "location of death, country")]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-PlaceOfDeath-extension')", "")]
public Dictionary<string, string> PlaceOfDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Decedent's Place Of Death. A Dictionary representing a place of death, containing the following key/value pairs: "placeOfDeathTypeCode" - place of death type, code "placeOfDeathTypeSystem" - place of death type, code system "placeOfDeathTypeDisplay" - place of death type, code display "placeOfDeathFacilityName" - place of death facility name "placeOfDeathLine1" - location of death, line one "placeOfDeathLine2" - location of death, line two "placeOfDeathCity" - location of death, city "placeOfDeathCounty" - location of death, county "placeOfDeathState" - location of death, state "placeOfDeathZip" - location of death, zip "placeOfDeathCountry" - location of death, country |
Examples
// Setter:
Dictionary<string, string> placeOfDeath = new Dictionary<string, string>();
placeOfDeath.Add("placeOfDeathTypeCode", "16983000");
placeOfDeath.Add("placeOfDeathTypeSystem", "http://snomed.info/sct");
placeOfDeath.Add("placeOfDeathTypeDisplay", "Death in hospital");
placeOfDeath.Add("placeOfDeathFacilityName", "Example Hospital");
placeOfDeath.Add("placeOfDeathLine1", "8 Example Street");
placeOfDeath.Add("placeOfDeathLine2", "Line 2");
placeOfDeath.Add("placeOfDeathCity", "Bedford");
placeOfDeath.Add("placeOfDeathCounty", "Middlesex");
placeOfDeath.Add("placeOfDeathState", "Massachusetts");
placeOfDeath.Add("placeOfDeathZip", "01730");
placeOfDeath.Add("placeOfDeathCountry", "United States");
SetterDeathRecord.PlaceOfDeath = placeOfDeath;
// Getter:
string state = ExampleDeathRecord.PlaceOfDeath["placeOfDeathState"];
Console.WriteLine($"State where death occurred: {state}");
Race
Decedent's Race.
Declaration
[Property("Race", Property.Types.TupleArr, "Demographics", "Decedent's Race.", true, 13)]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-race')", "")]
public Tuple<string, string>[] Race { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Tuple<System.String, System.String>[] | the decedent's race |
Examples
// Setter:
Tuple<string, string>[] race = { Tuple.Create("Non Hispanic or Latino", "2186-5"), Tuple.Create("Salvadoran", "2161-8") };
ExampleDeathRecord.Race = race;
// Getter:
foreach(var pair in ExampleDeathRecord.race)
{
Console.WriteLine($"\Race text: {pair.Key}: code: {pair.Value}");
};
Residence
Decedent's residence.
Declaration
[Property("Residence", Property.Types.Dictionary, "Demographics", "Decedent's residence.", true, 11)]
[PropertyParam("residenceLine1", "residence, line one")]
[PropertyParam("residenceLine2", "residence, line two")]
[PropertyParam("residenceCity", "residence, city")]
[PropertyParam("residenceCounty", "residence, county")]
[PropertyParam("residenceState", "residence, state")]
[PropertyParam("residenceZip", "residence, zip")]
[PropertyParam("residenceCountry", "residence, country")]
[PropertyParam("residenceInsideCityLimits", "residence, inside city limits?")]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "address")]
public Dictionary<string, string> Residence { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Decedent's residence. A Dictionary representing residence address, containing the following key/value pairs: "residenceLine1" - residence, line one "residenceLine2" - residence, line two "residenceCity" - residence, city "residenceCounty" - residence, county "residenceState" - residence, state "residenceZip" - residence, zip "residenceCountry" - residence, country "residenceInsideCityLimits" - residence, inside city limits? |
Examples
// Setter:
Dictionary<string, string> residence = new Dictionary<string, string>();
residence.Add("residenceLine1", "9 Example Street");
residence.Add("residenceLine2", "Line 2");
residence.Add("residenceCity", "Bedford");
residence.Add("residenceCounty", "Middlesex");
residence.Add("residenceState", "Massachusetts");
residence.Add("residenceZip", "01730");
residence.Add("residenceCountry", "United States");
residence.Add("residenceInsideCityLimits", "True");
SetterDeathRecord.Residence = residence;
// Getter:
string state = ExampleDeathRecord.Residence["residenceState"];
Console.WriteLine($"State of residence: {state}");
ServedInArmedForces
Whether the decedent ever served in the US armed forces. Corresponds to item 8 of the U.S. Standard Certificate of Death.
Declaration
[Property("Served In Armed Forces", Property.Types.Bool, "Demographics", "Whether the decedent ever served in the US armed forces.", true, 20)]
[FHIRPath("Bundle.entry.resource.where($this is Patient).extension.where(url='http://nightingaleproject.github.io/fhirDeathRecord/StructureDefinition/sdr-decedent-ServedInArmedForces-extension')", "")]
public bool ServedInArmedForces { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Boolean | Whether the decedent ever served in the US armed forces. |
Examples
// Setter:
ExampleDeathRecord.ServedInArmedForces = False;
// Getter:
Console.WriteLine($"Served In Armed Forces?: {ExampleDeathRecord.ServedInArmedForces}");
SSN
Decedent's Social Security Number.
Declaration
[Property("SSN", Property.Types.String, "Demographics", "Decedent's Social Security Number.", true, 12)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "identifier")]
public string SSN { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's social security number |
Examples
// Setter:
ExampleDeathRecord.SSN = "123-45-678";
// Getter:
Console.WriteLine($"Decedent Suffix: {ExampleDeathRecord.SSN}");
Suffix
Decedent's Suffix.
Declaration
[Property("Suffix", Property.Types.String, "Demographics", "Decedent's Suffix.", true, 5)]
[FHIRPath("Bundle.entry.resource.where($this is Patient)", "name")]
public string Suffix { get; set; }
Property Value
| Type | Description |
|---|---|
| System.String | the decedent's suffix |
Examples
// Setter:
ExampleDeathRecord.Suffix = "Jr.";
// Getter:
Console.WriteLine($"Decedent Suffix: {ExampleDeathRecord.Suffix}");
TimingOfRecentPregnancyInRelationToDeath
Timing Of Recent Pregnancy In Relation To Death. Corresponds to item 36 of the U.S. Standard Certificate of Death.
Declaration
[Property("Timing Of Recent Pregnancy In Relation To Death", Property.Types.Dictionary, "Medical", "Timing Of Recent Pregnancy In Relation To Death.", true, 48)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='69442-2')", "")]
public Dictionary<string, string> TimingOfRecentPregnancyInRelationToDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Timing Of Recent Pregnancy In Relation To Death. A Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "PHC1260");
code.Add("system", "http://github.com/nightingaleproject/fhirDeathRecord/sdr/causeOfDeath/vs/PregnancyStatusVS");
code.Add("display", "Not pregnant within past year");
ExampleDeathRecord.TimingOfRecentPregnancyInRelationToDeath = code;
// Getter:
Console.WriteLine($"Timing Of Recent Pregnancy In Relation To Death: {ExampleDeathRecord.TimingOfRecentPregnancyInRelationToDeath["display"]}");
TobaccoUseContributedToDeath
Did tobacco use contribute to death. Corresponds to item 35 of the U.S. Standard Certificate of Death.
Declaration
[Property("Tobacco Use Contributed To Death", Property.Types.Dictionary, "Medical", "Did tobacco use contribute to death?", true, 42)]
[PropertyParam("code", "The code used to describe this concept.")]
[PropertyParam("system", "The relevant code system.")]
[PropertyParam("display", "The human readable version of this code.")]
[FHIRPath("Bundle.entry.resource.where($this is Observation).where(code.coding.code='69443-0')", "")]
public Dictionary<string, string> TobaccoUseContributedToDeath { get; set; }
Property Value
| Type | Description |
|---|---|
| System.Collections.Generic.Dictionary<System.String, System.String> | Did tobacco use contribute to death. A Dictionary representing a code, containing the following key/value pairs: "code" - the code describing this finding "system" - the system the given code belongs to "display" - the human readable display text that corresponds to the given code |
Examples
// Setter:
Dictionary<string, string> code = new Dictionary<string, string>();
code.Add("code", "373066001");
code.Add("system", "http://github.com/nightingaleproject/fhirDeathRecord/sdr/causeOfDeath/vs/ContributoryTobaccoUseVS");
code.Add("display", "Yes");
ExampleDeathRecord.TobaccoUseContributedToDeath = code;
// Getter:
Console.WriteLine($"Did tobacco use contribute to death: {ExampleDeathRecord.TobaccoUseContributedToDeath["display"]}");
Methods
FromDescription(String)
Helper method to return a JSON string representation of this Death Record.
Declaration
public static DeathRecord FromDescription(string contents)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | contents | string that represents |
Returns
| Type | Description |
|---|---|
| DeathRecord | a new DeathRecord that corresponds to the given descriptive format |
GetAll(String)
Given a FHIR path, return the elements that match the given path; returns an empty array if no matches are found.
Declaration
public object[] GetAll(string path)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | path | represents a FHIR path. |
Returns
| Type | Description |
|---|---|
| System.Object[] | all elements that match the given path, or an empty array if no matches are found. |
GetFirst(String)
Given a FHIR path, return the first element that matches the given path.
Declaration
public object GetFirst(string path)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | path | represents a FHIR path. |
Returns
| Type | Description |
|---|---|
| System.Object | the first element that matches the given path, or null if no match is found. |
GetITypedElement()
Helper method to return an ITypedElement of the record bundle.
Declaration
public ITypedElement GetITypedElement()
Returns
| Type | Description |
|---|---|
| ITypedElement | an ITypedElement of the record bundle |
GetLast(String)
Given a FHIR path, return the last element that matches the given path.
Declaration
public object GetLast(string path)
Parameters
| Type | Name | Description |
|---|---|---|
| System.String | path | represents a FHIR path. |
Returns
| Type | Description |
|---|---|
| System.Object | the last element that matches the given path, or null if no match is found. |
ToDescription()
Returns a JSON encoded structure that maps to the various property annotations found in the DeathRecord class. This is useful for scenarios where you may want to display the data in user interfaces.
Declaration
public string ToDescription()
Returns
| Type | Description |
|---|---|
| System.String | a string representation of this Death Record in a descriptive format. |
ToJSON()
Helper method to return a JSON string representation of this Death Record.
Declaration
public string ToJSON()
Returns
| Type | Description |
|---|---|
| System.String | a string representation of this Death Record in JSON format |
ToXML()
Helper method to return a XML string representation of this Death Record.
Declaration
public string ToXML()
Returns
| Type | Description |
|---|---|
| System.String | a string representation of this Death Record in XML format |


Dear Brothers and Sisters,
Welcome to St. Anthony's!
You will notice on our homepage that it says, "Go make disciples!" This is our church's mission statement. In fact this mission, given to the disciples by the Lord Jesus, is the mission of the entire Catholic Church.
Undertaking this command of Jesus is twofold. First, it means that our own hearts have been transformed by His mercy and love because how could we offer to others what we have not received ourselves? This is only possible by first opening to Him who stands knocking at the door of our hearts. In time, this encounter grows and deepens through the great treasures He has given us through His Holy Church. Celebrating these gifts with a spirit of reverence, love and awe allows a space for the Holy Spirit to set our hearts on fire with Faith, Hope and Charity.
Then, once receiving, how could we keep the flame of his love all to ourselves? This fire which purifies, warms and enlightens, is meant to be spread and to grow brighter until the whole world knows Him and is set ablaze with His goodness and love. And so, we set out with hearts on fire, in our own little way, to bring the light of Christ into the world. Ultimately, it is not our work but, by His grace, we are made participants with Him in the salvation of our neighbor. What greater joy could there be than this?
So then, brothers and sister, rooted in the richness of our Catholic Faith, we set out together to transform the world one person at a time. Come and let us set out together.
With much love and affection,
Fr. Al
Would you like to know more about us?
Our address is Saint Anthony of Padua Church, 121 Bridge Avenue, Red Bank New Jersey 07701
You can come visit us, give us a call, or send us an email. We are happy to hear from you!
732-747-0813


PSI requires JavaScript. Please enable.
rotate locale
Reanalyze
Mobile
Desktop
Diagnose performance issues
See detailed analysis and recommendations from loading your site in a simulated environment.
🔗 http://thisurl.com
Diagnose performance issues
See detailed analysis and recommendations from loading your site in a simulated environment.
🔗 http://thisurl.com


Upload your image(s) and select a style
Choose an image style:
Fire Style
Gold Black Style
Pink Style
Triangle Style
Flame Style
Landscape Style
Rain Style
Starry Night Style
Mosaic Style
The Scream Style
The Wave Style


Next:
Contents
Contents
A Discrete EVent system Simulator
Jim Nutaro
Contents
About this manual
Building and Installing
Modeling and simulation with Adevs
Atomic Models
Network Models
Parts of a Network Model
The
route
method
The
getComponents
method
Illegal networks
Simulating a Network Model
A complete example of a network model
Digraph Models
Cell Space Models
Variable Structure Models
Building and Simulating Variable Structure Models
A Variable Structure Example
Continuous Models
Differential equation modeling with the
ode_system
class
Modeling hybrid systems with adevs and OpenModelica
The Simulator Class
Simulation on multi-core computers
Limits of the parallel simulator
Modifying your models to exploit lookahead
Partitioning your model
Partitioning and lookahead
A complete example
Managing memory across thread boundaries
Notes on repeatability and performance
Models with Many Input/Output Types
Alternate types for time
Random Numbers
Interpolation
About this document ...
rotten 2014-02-19


Blog Archive 2017 Structural and Relational Data Jul 05 2017 Particles and Waves May 24 2017 Versioning Better Than SemVer Jan 18 2017 2015 Rarely Reversible Apr 26 2015 2014 Unsound and Incomplete Jan 08 2014 2013 Slurp & Spit Jun 26 2013 Code Density Jun 24 2013 SemVer: A Technical Solution to a Social Problem Jun 19 2013 Trivial Cycles in Object Oriented Programming Jun 18 2013 Octopress Jun 17 2013 Fipp: Fast Idiomatic Pretty-Printer for Clojure Jan 11 2013 Factjor: Concatenative Clojure Jan 01 2013 2012 The Node.js REPL is Broken Dec 21 2012 Clojure’s multimethod dispatch as a library Dec 10 2012 Dataflow Solver (qplan for Clojure) Dec 01 2012 Templating: Clojure’s Backtick Nov 23 2012 ClojureScript Projects Nov 22 2012 Learn to Read the Source, Luke Apr 16 2012 REST: One Thousand Inconsequential Decisions Feb 26 2012 Plugging a hole in Microsoft’s hiring pipe: IE Frame Jan 14 2012 2011 One year after accidentally falling in love with Rails Sep 24 2011 Stupid brain trick: Tests and vertical splits Aug 16 2011 2010 Where Rails Rocks (and where Python doesn’t) Sep 17 2010 How two Pythonistas accidentally fell in love with Rails Sep 13 2010 NoScript Add-on Install Base Jun 04 2010 2009 ORMs and Declarative Schemas Oct 06 2009 URL routing and views Aug 24 2009 Dropping Django Aug 19 2009 AppWeek Jun 12 2009 PowerShell: condemned to reinvent Apr 20 2009 Language-oriented programming: too much, too fast Feb 09 2009 Break the cycle of broken builds Feb 03 2009 Contributions Jan 26 2009 2008 Rift is available on NXE! Nov 20 2008 Control flow has to flow Oct 27 2008 Imaginary APIs Oct 09 2008 Simplicity belongs in APIs Oct 08 2008 Why so serious? Sep 16 2008 Bug farms Sep 10 2008 Flexibility belongs in APIs Aug 28 2008 Computers are everywhere, you no longer have an excuse Aug 18 2008 Microsoft manages interns better than Google Jun 24 2008 Rift May 18 2008 A googol at Google May 12 2008 It is easier to pirate Windows than to install it legally May 10 2008 2006 When order doesn’t matter Mar 27 2006 Pythagoras was a smart guy Mar 27 2006 File systems for people Mar 27 2006 Computers should make life easier Mar 26 2006


| 1 | Rahul SharmaJobs | Floor CleaningCleaning the floor of the entire house | Rs. 100Price |
| 2 | Vinay GuptaJobs | ITR filingFilling ITR and uploading proof of investment | Rs. 150Price |
| 3 | Driver needed to prevent drunk drivingJobs | MercedesNeed to drop the client safely at his home by driving in client's car | Rs 100Price |
| 3 | {{item[0]}}Jobs | {{item[1]}}Need to drop the client safely at his home by driving in client's car | Rs {{item[2]}}Price |


[§844D-85] Confidentiality of computer software and database structures. To maintain the computer system security of the state DNA database and data bank identification program, the computer software and database structures used by the DNA laboratory of the department to implement this chapter are confidential. [L 2005, c 112, pt of §1]


Listen to events
Izanami provide a way to listen what is happening inside. There is two to achieve that :
- SSE
- Webhooks
Events model
An event is json with the following structure :
{
"_id":<PHONE_NUMBER>01863450,
"type": "CONFIG_UPDATED",
"key": "demo:title",
"domain": "Config",
"payload": {
"id": "demo:title",
"value": "{\n \"title\": \"Changed title\"\n}"
},
"oldValue": {
"id": "demo:title",
"value": "{\n \"title\": \"Title\"\n}"
},
"timestamp": "2017-12-18T11:01:00.469"
}
| Field | Description |
|---|---|
_id |
Unique id of the event. A recent id is greater than a previous |
type |
The type of the event (see the chapter below) |
key |
The key of the modified object. |
domain |
The domain concerned by the event (see the chapter below) |
payload |
The json of the updated object |
oldValue |
The oldValue is optional and only present during an update. |
timestamp |
The timestamp of the event |
The field oldValue
is optional and only present during an update.
Domains
| Domain | Description |
|---|---|
| Experiment | Events from experiments, bindings and experiment events |
| ApiKey | Events from api keys |
| Config | Events from configs |
| Feature | Events from features |
| User | Events from users |
| Script | Events from scripts |
| Webhook | Events from web hooks |
Types
| Types | Description |
|---|---|
CONFIG_CREATED |
When a config is created |
CONFIG_UPDATED |
When a config is updated |
CONFIG_DELETED |
When a config is deleted |
CONFIGS_DELETED |
When configs are deleted |
FEATURE_CREATED |
When a feature is created |
FEATURE_UPDATED |
When a feature is updated |
FEATURE_DELETED |
When a feature is deleted |
FEATURES_DELETED |
When features are deleted |
GLOBALSCRIPT_CREATED |
When a global script is created |
GLOBALSCRIPT_UPDATED |
When a global script is updated |
GLOBALSCRIPT_DELETED |
When a global script is deleted |
GLOBALSCRIPTS_DELETED |
When global scripts are deleted |
USER_CREATED |
When a user is created |
USER_UPDATED |
When a user is updates |
USER_DELETED |
When a user is deleted |
USERS_DELETED |
When users are deleted |
WEBHOOK_CREATED |
When a webhook is created |
WEBHOOK_UPDATED |
When a webhook is updated |
WEBHOOK_DELETED |
When a webhook is deleted |
WEBHOOKS_DELETED |
When webhooks are deleted |
APIKEY_CREATED |
When an apikey is created |
APIKEY_UPDATED |
When an apikey is updated |
APIKEY_DELETED |
When an apikey is deleted |
APIKEYS_DELETED |
When apikeys are created |
EXPERIMENT_CREATED |
When an experiment is created |
EXPERIMENT_UPDATED |
When an experiment is updated |
EXPERIMENT_DELETED |
When an experiment is deleted |
EXPERIMENTS_DELETED |
When experiments are deleted |
VARIANT_BINDING_CREATED |
When an binding is created |
EXPERIMENT_VARIANT_EVENT_CREATED |
When an experiment event is created |
EXPERIMENT_VARIANT_EVENT_DELETED |
When an experiment event is deleted |
Web hooks
Web hooks allow you to get notified when events occurred in izanami. You have to register an endpoint in izanami, the endpoint needs to be a POST api handling a json payload of the form :
{
"objectsEdited": [
{...},
{...}
]
}
If the call to the registered endpoint failed too much, the registered web hook will be deactivated.
Server sent event
Server sent event allow the server to push event to a client. The server keep a connection opened to send notifications. The Server-Sent Events EventSource API is standardized as part of HTML5 by the W3C.
Izanami expose server sent events endpoint to listen what is happening. There is two endpoint:
/api/events?domains=Config,Feature&patterns=*
: a global listener/api/events/Config?patterns=*
: a listener for a specific domain
curl -X GET \
'http://localhost:9000/api/events?domains=Config,Feature&patterns=*' \
-H 'Content-Type: application/json' \
-H 'Izanami-Client-Id: xxxx' \
-H 'Izanami-Client-Secret: xxxx'
Will return
id:<PHONE_NUMBER>79392517
data: {"_id":942740804979392517,"type":"FEATURE_UPDATED","key":"drop:hbomb:in:random:place","domain":"Feature","payload":{"id":"drop:hbomb:in:random:place","enabled":false,"parameters":{"releaseDate":"11/01/2018 09:58:00"},"activationStrategy":"RELEASE_DATE"},"timestamp":"2017-12-18T13:58:17.841","oldValue":{"id":"drop:hbomb:in:random:place","enabled":false,"parameters":{"releaseDate":"11/01/2018 09:58:00"},"activationStrategy":"RELEASE_DATE"}}
Replay Events
If you’re using kafka as a data store for events, you can replay events from the last day using the Last-Event-Id
header.
With this request, the event after the id<PHONE_NUMBER>79392517
will be replayed.
curl -X GET \
'http://localhost:9000/api/events?domains=Config,Feature&patterns=*' \
-H 'Content-Type: application/json' \
-H 'Izanami-Client-Id: xxxx' \
-H 'Izanami-Client-Secret: xxxx' \
-H 'Last-Event-Id:<PHONE_NUMBER>79392517'
The replay can be used for failure handling while listening to events. If the client lose the connection or crash, it can specify the last event id to get the event that append since the failure.


The Dogulean Planetarium
Quick Start
By all means just Enter the
Planetarium and try things out. But note:
-
You can change the direction of view by holding the left
mouse button down and dragging the mouse. With a
touchpad press with one finger and drag.
-
You can change the scale of the display (zoom or unzoom)
by turning the mouse wheel or by holding down the mouse
and moving the mouse up or down. With touchpad,
get this effect by dragging two fingers vertically,
without pressing. With a Mac OS X-type mouse (MS now has
similar mice) stroke two fingers on the mouse.
-
Right-clicking anywhere will bring up a control panel.
Right-clicking again or clicking "Dismiss" will dismiss
it. With a touchpad, press with two fingers, or possibly
press on the lower right corner of the touchpad.
-
You can drag the control panel by its top line.
-
NEW! You can choose what planet you are on,
including the Sun. If the planet is not the Earth or the
Moon, then the main thrill of this is to see your planet
against the stars. For that, there is an altitude setting
(altitude as a multiple of planet radius). You want to
look down (set View/Elevation to -89) and then ramp the
altitude up (under "Viewer Location"). Another thrill is
to go to an outer planet, blow up planet size, and look at
the inner planets clustered around the Sun. Lines of
latitude and longitude and the ecliptic will be drawn
appropriately for the planet you are on and the planet will
rotate at about the right speed.
-
Besides the obvious sliders, select boxes, etc., anything
that changes color when you mouse-over it can be clicked on
with some effect or other.
-
If you put the mouse on any heavenly body a "tooltip" should
appear, telling you what it is and its position.
-
Clicking the left mouse button (without dragging) cycles through constellation,
star, and planet labels.
- No labels.
- Planet names, constellation names, names of well-known
stars, letters of fairly bright stars.
- Constellation names, designations for stars, but no
planet names. All stars will have labels in
this mode, but things will be rather cluttered and not
all labels will appear until you zoom in.
With a touchpad, this would be just a touch or possibly a click.
Source Code
See our github
planetarium repository.
The Planetarium On Laptop or Desktop
Requirements and Recommendations
-
You need a browser that supports HTML5 and WebGL,so the
system needs to support OpenGL. A reasonably recent
middle-of-the-line graphics processor should do.
-
Chrome, Opera, Firefox, and
IE 11 are all ok on Windows or Linux. Chrome and Opera are
best and perform about the same.
-
I haven't tried the Planetarium on Apple OS X. Chrome, Opera,
and Safari should all perform about the same.
-
A reasonably high-definition monitor should suffice, but
higher definition is better. A big UHD TV is excellent!
Controls and Settings in Detail
All settings are saved, so if you reload the page, or close it and
then revisit it some time later, it will be in the same state.
Viewer Location
By default, the Planetarium will try to use the HTML5 geolocate
function to set your latitude and longitude. If you want to be in
some other place, any map web site will tell you its coordinates
and you can enter them manually.
View
Elevation (altitude) and Rotation (azimuth)
determine the direction of view. Dragging the mouse has the
same effect—a drag changes elevation by an angle
determined by the vertical part of the drag, rotation by the
horizontal part.
Zoom magnifies everything and thereby reduces the field of
view, like using a telescope.
Lines, when ON displays reference lines of right ascension
and declination, as well as the ecliptic.
-
Lines of right ascension are spaced 15 degrees (one hour) apart,
lines of declination 10 degrees apart. The lines are not
labeled, but you can mouse-over a nearby object to find
what a line represents.
-
The equator and 0° and 180° meridians are in
gold, the ecliptic in magenta.
-
The reason that the lines of right ascension, the equator,
and the ecliptic appear as straight lines is that they are
all great circles. Lines of declination other than the
equator look curved because they are not great circles.
Time
Time Currently Set shows the current date and time of the
app in format YYYY-MM-DD hh:mm:ss.sss.
If Use Real Time is enabled and you click it, the app will
start using the time your computer's current time as its
internal time will be set to your computer's current time in
GMT/UTC and the time rate will be set to 1. If you are already
on real time, this line will be disabled.
The clock Rate can be set to any number from -60 (clock
runs one minute per real second backwards) to 60 (one minute per
real second forward).
- The "1" button will set the rate to 1 ("normal" passage
of time) and the "0" button will set the rate to 0, stopping
the clock.
Real time is the default.
Stars
We model stars as disks, placed far away in the "sphere of fixed stars".
For the Planetarium, current technology has two shortcomings:
-
Monitor resolution is far lower than that of the sky.
-
Pixels have a maximum brightness that is not very high at all.
We try to compensate for these shortcomings by providing size
and brightness settings for you to use according to taste. At
present, I don't have any scientific basis for recommending
particular settings.
Base Radius. If "Brightness Boost" is 1, a white magnitude
0 star will be represented by a disk of radius 1 and color
rgb(1.0, 1.0, 1.0) (equivalently 0xFFFFFF). Stars that are
brighter will have a bigger radius so the amount of light emitted on
screen is equivalently bigger than that of the maginitude 0 star.
Stars that are dimmer than magnitude 0 will just be dimmer.
Stars that are not white will have their size or brightness
boosted by a factor of 3*max(r, g, b)/(r + g + b).
Brightness Boost is a number by which to multiply the
brightness of stars before computing the radius and
RGB components to use for it.
We derive a color for each star from the B – V value given
for it in the star catalog we use. The Color level value
determines how intense this color will be. A level of 0 means
all stars are white. At level 10, colors are very striking. In
between, reds and yellows are noticeable but blues tend to just
look a bit dim.
Planets
We model planets as spheres orbiting the Sun. Their diameters
are scaled from their actual diameters and the orbital positions
are computed using their Keplerian orbital elements. Their light
is the Sun's light reflecting off them.
Sun and Moon are treated as planets, but differently from the
others because they appear much larger in the sky and because
the Sun shines. The Earth is a planet, too, but a rather
different one because we are on it and have to take account of
its inclination and rotation.
Planet Magnification multiplies the apparent size of
planets other than the current home planet, the Sun, possibly
the Moon or Earth—see Sun/Moon/Earth Magnification below.
 Moderate magnifications will also let you make out the
phases of Venus and Mercury.
Planet Color has four options: Green, Blue, White, and Natural. These
do not apply to Sun, Moon, or Earth, which always have a natural
color.
-
Green. There are no green stars, so this makes the
planets easy to pick out.
-
Blue makes the planets light blue. If you are
red-green color-blind, try setting the Color Level for stars
to 0 and using this option.
-
White, the brightest.
-
Natural. Except for the Sun and Venus, for which I
do not have a good Mercator projection image, "natural" now
represents each planet using an image of it.
Sun/Moon/Earth Magnification. At their real size Sun and
Moon look too small—although they look big in the sky,
but each subtends only half a degree. The default magnification
of 5 seems about right for normal use. If Mercury is near the
Sun but in front of it, turning up the Sun/Moon magnification may help
find Mercury as a small speck on the Sun. If the current home
planet is the Earth, then this setting affects the size of Sun
and Moon. If the home planet is the Moon, then it affects the
size of Sun and Earth. If the home planet is the Sun, it
doesn't affect anything. Otherwise it affects only the Sun.
Sun Brightness. How to set the brightness of the Sun is
art rather than science. A level of 5 or 10 seems reasonable.
This will make the Moon and planets brighter, but only to a
certain degree, since the maximum value of 1.0 for each RGB
component still applies to them.
The Planetarium On a Mobile Device
The point of using the Planetarium on a mobile device is that you
can take it outside to and see what stars there are.
The Basics
Platforms: A moderately recent, middle-of-the-line or better
smartphone or tablet should do.
Browser:
- On Android, use Chrome or Opera. Opera seems best.
Firefox is too slow.
- On iOS, Safari, Chrome, Firefox, and Opera all seem to be
different skins on the same thing, so they are all equally
good.
When you open the Planetarium, a Mobile Setup menu will
appear.
You can get this menu at any time by touching the "Setup"
button on the planetarium screen.
Dismiss the setup menu by touching "Done Setup".
Key items on the Menu
-
Your location. Touch "Set Location From GPS" whenever you use
the Planetarium far enough from your last location that it
matters. If it doesn't work, set it manually, if you know
your approximate latitude and longitude.
You need to set at least an approximate location
in order to see the sky as it is where you are.
-
If your phone has a gyroscope, under "Navigation" you will
have a choice about whether to use the automatic orientation
of your phone by the gyroscope ("Just point your device") or
not ("Drag one finger …"). If you have the choice,
normally you will want to choose "Just point …".
-
If your phone supports device orientation control (has a
gyroscope), the view will show the part of the sky above the
point where the end of your phone is pointing, if the
Planetarium knows which way north is.
-
If your phone has a compass, the Planetarium will
automatically find the direction it is pointing from that
when the Planetarium opens. If you think that the
Planetarium's direction seems off, you may want to re-set
it. Stay away from any electrical or magnetic fields
(such as TVs or monitors) or from masses of magnetic metal
when using the compass.
-
If your phone doesn't have a compass (e.g. if it is an
iPod touch) or if it is too much trouble getting the
compass to work properly, point the end of your phone
north (e.g. toward the north star) and press "Set True
North".
-
On Android, when you leave this menu, the page will request to
go full screen, so (hopefully) you won't see the address bar
while looking at the stars. Quite a lot of things will bump
you out of full screen, but if you want to you can get it back
by returning to this menu and dismissing it.
-
To learn the angle at which you need to hold the phone, try getting something
familiar, like the Sun, on the screen.
The other items on the menu are the ones available on the
desktop. You probably don't want to fiddle a lot with the menu on
a small screen, but if you are familiar with the menu, you might
want to use it now and then.
Note: On iOS, sliders and data entry boxes on submenus
of the settings menu are very small, but
the system enlarges them if you touch them.
Labeling Stars
The Planetarium can show three levels of star labels.
Touch the screen to change levels.
-
Level 0 (default on desktop): no labels.
-
Level 1 (the default on mobile devices): Names of well-known
stars, letters for fairly bright stars. You should be able to
make out the shapes of constellations.
-
Level 2: Constellation names, designators for all
stars, but no planet names. Things will be rather
cluttered and not all labels will appear until you
zoom in. In particular, for stars that have no
designation but their bright star number, the number
will not appear until zoom is at least 1.8.
Issues and Limitations
-
Objects are distorted (stretched), especially near the edges of the
screen. This is due to the nature of the projection of the model onto
the screen,
-
So far, Messier objects (nebulae) are not represented.
-
Refraction effects near the horizon are not modeled.
-
Oblateness is modeled as far as viewing them goes, but does
not affect camera direction as it should.
Methods and Background
A Planetarium or Star Map Implemented in WebGL and three.js
The idea of implementing a planetarium using a 3-D graphics system
is an obvious one. We do it this way:
- Put the "fixed" stars far away at positions given in a star catalog.
- Put the Sun in the middle.
- Compute the heliocentric positions of the planets and the
geocentric position of our Moon.
- Put a "camera" at the observer's location on Earth and let
the observer point it in the desired direction.
- Let the 3-D system do the rest.
The model must be much the same as Kepler's model of the solar
system, and the method of computing the positions of the planets
is just a modernization of his in which the parameters change with
time.
With WebGL, this can be done on a web page that anybody can access;
and, with the three.js library, the 3-D part of the programming is relatively
easy.
Using this application is supposed to be like looking at the night
sky–even when it is daytime in the app.
Stars
Most star data comes from the 2017 US Naval Observatory
Table of Bright Stars.
We convert star magnitudes to brightness according to the
formula in the
Wikipedia Magnitude
article. Converting the brightness number to screen values is a
matter of judgement which depends on the value chosen for a
reference brightness.
Star colors are derived from the B – V color index of
the star using a rough method derived from the table in a
Cornell Ask
an Astronomer answer. I would be happy to know a better
way of doing it. The Bright Stars Table also contains the V - I
color index, so we could use a method that relies on both.
Most common names of stars come from the
Wikipedia Proper
Names of Stars article.
Planets
For planets other than the Sun (which is at the origin) and Moon,
positions are computed from their Keplerian elements as given
in Keplerian
Elements for Approximate Positions of the Major Planets by
E. M. Standish. Thanks to the miracle of the WebGL graphics
engine, we only need to compute the heliocentric positions of
the planets. The WebGL engine does the work of converting those
to positions in the sky relative to the observer.
The main reason for computing planet positions instead of
getting them from ephemerides is that we want positions in
space rather than in the Earth's sky. A second is to avoid
dependencies on other sites.
Although we do compute the right ascension and declination of
planets to display in their tooltip description, we actually set
their position in the solar system using their
heliocentric ecliptic coordinates and then tilt the solar system
by the J2000 obliquity of the Earth and then tilt the Earth back
so that its north pole points to the celestial north pole.
The orbit Moon around the Earth is much more difficult to compute,
because the Moon is subject to gravitational pull of both Earth
and Sun, to the influence of the tides, and to much else. I have
borrowed Javascript code to do this from
Martin Vézina's Planet
Positions project, which was itself translated from Matlab
code by David Eagle, based in turn on programs in Lunar Tables
and Programs From 4000 B.C. TO A.D. 8000 by Michelle
Chapront-Touzé and Jean Chapront.
Data on radii, oblateness, and rotation rates of planets are taken
from NASA
planetary fact sheets.
Planet textures come from various sources.
I have used the numeric.js
javascript library to determine star
and planet label positions.


{% extends 'jobboard/base.html' %} {% load account socialaccount i18n %} {% block head_title %} Vera Platform - Profile settings {% endblock %} {% block content %} {{ block.super }}
{% trans 'The following e-mail addresses are associated with your account:' %}
{% trans 'Warning:' %} {% trans "You currently do not have any e-mail address set up. You should really add an e-mail address so you can receive notifications, reset your password, etc." %}
{% endif %} Manage emails
{% for base_account in user.socialaccount_set.all %} {% with base_account.get_provider_account as account %}- {{ account.get_brand.name }}
{% endwith %}
{% empty %}
- You have no social apps added.
{% endfor %}
Manage social accounts


Kenneth Hahn Disc Golf Club
Home
About
Events
Scores
(current)
Contact
Kenneth Hahn Disc Golf Club
Come out and shoot a round with us!
Submit Your Score
Your Name:
Score:
Date Played:
Score List


This is a paragraph of text which has only one stylesheet applied to it. That style causes the first line to be gray. No other lines will be gray.


15-30 from 700
| Scott Ruiz |
Welcome to our service
It's a pleasure to have you on our service..
|
(3) | 2 min ago | |
| Roger Hart |
Your subscription was updated
We are glad you decided to go with a vip..
|
(2) | 10 min ago | |
| Scott Ruiz |
Update is available
An update is under way for your app..
|
25 min ago | ||
| Sara Holland |
New Sale!
You had a new sale and earned..
|
(1) | 30 min ago | |
| Amy Hunter |
Action Required for your account!
Your account is inactive for a long time and..
|
1 hour ago | ||
| Scott Ruiz |
New Photo Pack!
Our new photo pack is available now! You..
|
2 hrs ago | ||
| Ann Parker |
Product is released!
This is a notification about our new product..
|
(1) | 1 day ago | |
| Roger Hart |
Now on Sale!
Our Book is out! You can buy a copy and..
|
(9) | 1 day ago | |
| Lisa Gordon |
Monthly Report
The monthly report you requested for..
|
(6) | 3 days ago | |
| Roger Hart |
Trial Started!
You 30-day trial has now started and..
|
3 days ago | ||
| Julia Cole |
Invoice #INV001645
This is the invoice for the project we..
|
5 days ago | ||
| Vincent Sims |
Friend Request!
You have a new friend request. Click the..
|
(5) | 1 week ago | |
| Walter Fox |
Enjoy life!
Thank you for helping us with our cause...
|
(3) | 1 week ago | |
| Bruce Edwards |
New Twitter follower!
You have a new follower, congratulations..
|
(1) | 2 weeks ago | |
| George Stone |
Huge Discount available!
Due to the fact that you are a great..
|
3 weeks ago |


Solar panels
are devices that convert light into electricity. They are called "solar" panels because most of the time, the most powerful source of light available is the Sun.Unlike fossil fuels, solar energy doesn't produce the harmful pollutants. Solar energy is a clean and sustainable source of energy that you can use. Source
Consists of 6 panels
Perfect for smaller houses
Possible savings: 393 SAR/month
Consists of 12 panels
Perfect for small working families with a pool
Possible savings: 749 SAR/month
Consists of 18 panels
Perfect for medium to large households
Possible savings: 1311 SAR/month


When you open a model, you open it in a model editor. The model editor has three pages: The Model Overview Page and Advanced Options Page specify the model. The Model Checking Results Page shows you either what the model checker is doing while it runs, or what it did the last time it was run. You can switch between the pages using the tabs at the upper-left of the model editor view, or with the Alt+PageUp and Alt+PageDown keys.
You edit these pages in the usual way. Sections can be opened or closed by clicking the + or - . When entering text in fields, you can use your system's standard editing commands.
Whenever you enter a TLA+ expression as part of the model, that expression can use any symbols that you could use in a new definition placed at the end of the spec's root module. It can also contain any model values that are declared in the model, as well as additional definitions entered in the Additional Definitions section of the Advanced Options Page.


Install Chromium Extensions
Click to install
?
close
Configure to intsall
Navigate to
chrome://flags/#extension-mime-request-handling
Change configuration to
Always prompt for install
Relaunch and start installing.
Install
Go to
Chrome Store
Find the extension and copy the URL
Paste the clean URL and click the button.


Skipper
Play Shuffled
Play in Order
How close to the end of the song before we skip it?
1 second
2 seconds
3 seconds
4 seconds
5 seconds
6 seconds
« Previous
Next »
Drag and drop a playlist here


holmes-web theme Cosmo, made by Thomas Spark and licensed under Apache License v2.0.
detective icon public license according to https://www.iconfinder.com/icons/104623/detective_interrogation_icon#size=128.
holmes is a free open-source project and is composed of holmes-web and holmes-api.
Copyright globo.com - MIT Licensed - 2013


👋🏽
We need a few more pieces of information to finish setting up the app. This page will track your progress and show which steps you've completed with a checkmark (✅).
This is a basic system that uses Phaxio's API to send faxes. To set it up for yourself or your own friend group, you'll need a developer account from Phaxio, which is out of scope of this document.
Once you have a funded Phaxio account, you'll need two codes from Phaxio's API Keys.
Account Credentials
You'll need your "API Key" and "API Secret", both of which are in Phaxio's console. These are secrets, so be sure not to share them with anyone! The values in .env
are only visible to the owner of the project, so you can safely paste them there:
# find these at https://console.phaxio.com/api_credentials
PHAXIOKEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
PHAXIOSECRET=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
A Secret!
This app will send a real fax to a phone number and charge you money for doing so, and we don't want just anyone to be able to do that! Pick out a secret phrase or password you can use to make sure only you and your friends can send a fax from the app, and add it to .env
# let's not let just anyone fax you
SECRET=XXXXXXXX


Audit Risk refers to the possibility that the auditors may unknowingly fail to appropriately modify their opinion on finance statements that are materially misstated.
Relevant assertions are those that, without regard to the effect of controls, have a reasonable possibility of containing a misstatement that could cause the financial statements to be materially misstated.


What can England expect at Euro 2020?
England will return to Wembley for each of their opening three pool matches at Euro 2020.
England secured their place at Euro 2020 with a 7-0 thrashing of Montenegro at Wembley on Thursday night.
Here, the PA news agency takes a look at what lies ahead for the Three Lions next summer.
Where will England play?
Gareth Southgate’s side have qualified top of Group A, which means England will return to Wembley for each of their opening three pool matches at Euro 2020.
Although the full draw does not take place until the end of November, England are set to be in Group D.
For the first time in the competition’s history, the finals are being held across Europe.
Wembley will also host a game in the round-of-16, as well as both semi-finals and the final.
England, though, face at least some matches away from London, should they make it to the knock-out stage.
If Southgate’s men progress as group winners, they could play in Dublin and then on to a quarter-final trip to Rome.
Should they end runners-up, then plot a course for Copenhagen and St Petersburg, while a best third-place finish could see England head to Glasgow or perhaps Budapest in the last 16.
So who could England face?
England will be expecting to be in the pot for the top seeds, which is determined by performance during the qualification campaign.
The best six nations will be ranked on points – although not against the lowest team in the groups – and goal difference, so another win in England’s final qualifying match away to Kosovo would provide a welcome boost.
There could, though, be some heavyweights in the second pot, including Euro 2016 winners Portugal, who are behind Ukraine in their qualifying group, and possibly France if the world champions fail to finish ahead of Turkey.
Sounds great – how do I get a ticket?
The next window to apply for tickets will be in December following the finals draw but these will only be made available to supporters through the national associations.
As ever, demand – especially for England games at Wembley – is expected to exceed supply.


AWS re:Invent 2019: Beyond eleven nines: Lessons from Amazon S3 culture of durability (STG331-R1) Amazon S3 is well known for being designed for eleven nines of data durability. But durability is much more than a formula and a metric. It influences every aspect of how we design, build, deploy, and operate Amazon S3. In this session, learn about some o...
Hyperping | Uptime monitoring with public status pages Uptime monitoring for websites and APIs, public status pages, instantly receive alerts by emails, Slack and SMS
Examples of calling an API HTTP GET for JSON in different languages - Joe Kampschmidt's Code A list of code examples in various languages that demonstrate how to perform an HTTP/HTTPS GET for JSON on an API in different coding languages.
Make your SQLite bulk inserts very fast in C# .NET - Joe Kampschmidt's Code Learn how to increase performance with performing bulk SQLite inserts in C# .NET
Carl Franklin's Blazor Road Show! Thu, Feb 13, 2020, 6:00 PM: Our Agenda:• 6:00pm - 6:30pm: Food & networking• 6:30pm - 8:00pm: Introductions & Our featured speakerHi everyone, we'll be kicking off 2020 with a great speaker: Carl Fran
Valid Lovely Triangles - Numberphile Discover Valid Lovely Triangles Numberphile T-Shirt from Numberphile, a custom product made just for you by Teespring. With world-class production and customer support, your satisfaction is guaranteed.
Compilers: The Next Frontier In Web Performance - Chad Hietala - JSConf US 2018 ,"assets":{"js":"/yts/jsbin/player_ias-vfl0m8XVi/en_US/base.js","css":"/yts/cssbin/player-vflnCF_bL/www-player-webp.css"},"args":{"watermark":",https://s.ytimg.com/yts/img/watermark/youtube_watermark-vflHX6b6E.png,https://s.ytimg.com/yts/img/watermark/you...
WACUP (WinAmp Community Update Project) This is an update project which expands upon the patched Winamp 5.666 release by fixing issues with as well as providing new features and just doing something to help keep Winamp alive!
dapr/dapr Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge. - dapr/dapr
ReactSharp - A C# library for building web user interfaces public class Counter : ReactComponent { private int value = 0; void Increment() { SetState(() => { value++; }); } void Decrement() { SetState(() => { value--; }); } ...
SamProf/ReactSharp C# library for building web user interfaces. Contribute to SamProf/ReactSharp development by creating an account on GitHub.
Performance traps of ref locals and ref returns in C# | Premier Developer The C# language from the very first version supported passing arguments by value or by reference. But before C# 7 the C# compiler supported only one way of returning a value from a method (or a property) – returning by value.
extern alias - C# Reference You might have to reference two versions of assemblies that have the same fully-qualified type names. For example, you might have to use two or more versions of an assembly in the same application. By using an external assembly alias, the namespaces from ...
davidfowl/Todos Various todo list backend API implementations. Contribute to davidfowl/Todos development by creating an account on GitHub.
Visual Studio for Mac: Refresh(); event Join our free, virtual event to learn how Visual Studio for Mac integrates modern .NET developer tasks and platforms and makes web, mobile and game development easy and productive on your Mac
Microsoft for Startups – Building Startups | Microsoft for Startups Over the next two years, Microsoft has pledged 500 million dollars to support startups with access to technology, community spaces, and sales opportunities. Find resources to accelerate the growth of your startup.
Steve Gordon - Adventures in ASP.NET Core My blog where I discuss ASP.NET Core and .NET Core development.
RunAsRadio - Home RunAs Radio is a weekly podcast for IT Professionals working with Microsoft products. Each 30-minute episode covers a specific topic in the field of IT from a Microsoft-centric viewpoint.
.NET Rocks! vNext .NET Rocks! is a weekly talk show for anyone interested in programming on the Microsoft .NET platform. The shows range from introductory information to hardcore geekiness.


Major Mines in British Columbia
Use the list below to navigate to information on individual mine sites. Click on any mine to go directly to its profile page, or click the ‘+’ sign to expand the list item to see basic information (e.g., operator, ownership, commodity/ies produced) about that mine. You can also use our interactive map to navigate to information on individual mines across British Columbia.
Can't find what you're looking for? Please contact us here.
| Mine Name | Permittee | Mine Type | Operating Status |
|---|---|---|---|
|