For Comment Feedback for: date of type Quantity or string on all FHIR entities

[teslajoy]

What were you reviewing?

All FHIR resource entities

Suggested Improvements:

Enable one to many date of type Quantity or string on all entities. Example:

• dateQuantity -> Quantity integer with unit definitions ex. days
• dateString -> string representing a date (could place restrictions on how this string may be validated as date. ex. ^\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12]\d|3[01])$)

further examples in research:

• Specimen
  • Index collection date days
  • Index run date days
• Condition or Patient/Participant
  • Days to last followup
• Patient/Participant
  • Days to death

[RobertJCarroll]

Thanks for this comment. I think we need to look into making a couple of things more clear:

1. The use of relativeDateTime to allow use of "time quantities" (this exists already, but it may not be clear). This already exists everywhere we have dates (as a standard FHIR extension), but it likely isn't clear.
2. Some of these features, eg, age at death and age at follow up, do have specific homes.

[teslajoy]

Hi - we can possibly close this and follow through #83 on temporal data mappings.

[JamedFV]

Sounds good @teslajoy -- closing this out now