Stream: implementers
Topic: Coded Age Ranges
Jose Costa Teixeira (Jul 26 2020 at 12:47):
Is there any guidance or approach to using Age range as codes?
I want to define a few groups:
- baby
- child
- teenager
- adult
Jose Costa Teixeira (Jul 26 2020 at 12:48):
I could e.g. define an extension on the Range datatype to add a coded element. Or I could do something else... any ideas?
Lloyd McKenzie (Jul 26 2020 at 14:04):
@Bryn Rhodes
John Moehrke (Jul 27 2020 at 12:42):
@Keith Boone just got a codeSystem published for this purpose by IHE for public health reporting
John Moehrke (Jul 27 2020 at 12:43):
see https://github.com/IHE/fhir/blob/master/CodeSystem/codesystem-IHE_ADX_agerange.xml
Jose Costa Teixeira (Jul 27 2020 at 13:12):
Thanks but I'll have to define some codesystems myself - the question is where to use them.
Michael Lawley (Jul 27 2020 at 23:57):
What are your definitions for these categories? Are they universally understood? "Adult" in particular would seem to vary depending on context (16+, 18+, 21+) -- I would strongly advise including the age range in the codes' display text, also clearly accounting for boundary conditions where they need to be disjoint
Jose Costa Teixeira (Jul 28 2020 at 08:33):
Indeed, we will need to add the display text in several languaes. And these ranges they are locally defined for each scope.
The question is where to add them in a FHIR profile.
Jens Villadsen (Jul 28 2020 at 10:42):
display text across different languages will only make it worse I think. Adult/adulthood eg. is both a cultural thing, a mental thing, a physical thing and a jurisdictional thing.
Jose Costa Teixeira (Jul 28 2020 at 11:00):
This is for Belgium
Jose Costa Teixeira (Jul 28 2020 at 11:02):
Same jurisdiction, same culture (well...), but different languages in the same meeting
And it makes things interesting, not always worse :D
Jose Costa Teixeira (Jul 28 2020 at 11:05):
even if it were only for one language, the question applies: where to put a new element called "age range" - whatever the values?
@Bryn Rhodes or anyone?
Michael Lawley (Jul 28 2020 at 12:04):
I think I'm confused about what you actually want to do. I had assumed you wanted to define a CodeSystem with a set of codes corresponding to each of your ranges?
Jose Costa Teixeira (Jul 28 2020 at 12:29):
I have that codesystem. The question is where to use it in a Condition or Immunization resource
Jose Costa Teixeira (Jul 28 2020 at 12:34):
I expect an extension, but an extension to the resource? to the element? to the datatype?
Bryn Rhodes (Jul 28 2020 at 13:13):
I think it depends on the resource you're applying it to. If it's applied to Condition, I assume that would mean the range of onset-abatement? Which would I think require a resource level extension, since it's applying across elements. But for Immunization, it's applying to the occurrence element and could be defined there. A larger question, if you know what the age ranges are, is there a reason you wouldn't just represent the information directly in the appropriate elements of resources that could? Condition, for example, allows Age (and Range) for onset and abatement.
Last updated: Apr 12 2022 at 19:14 UTC
