Stream: implementers
Topic: controlled terminology code for my measurements
Christi Yuting Kao (Feb 11 2020 at 20:17):
Hello all, I'm new to FHIR and I'm trying to tramsform my raw text data file into the FHIR resource format. I'm having some questions and need guidance to see my approach is appropriate. Thank you veru much in advance!
- If I can't find controlled terminology code (for example, SNOMED or LOINC) for my measurements, I use text instead to describe the measurement. The measurements including: Rotation rate (x,y,z axis), acceleration (x,y,z axis) from apple watch accelerometer and gyroscope, type of utensil (fork, hand, ...) used during the meal and datetime the meal was started/end. I couldn't find appropriate controlled terminology for my measurements so I use text to describe, for example:
"code": {
"text": "acceleration"
}
- Use observation resource for meal time and utensil records.
My raw data in txt file (Time:Event observed):
2019-05-23 17:01:31 +0000: meal started
2019-05-23 17:10:37 +0000: meal completed
2019-05-23 17:16:07 +0000: utensil used is 3
This data is saying the subject started meal at 17:01 and completed the meal at 17:10, the utensil he used is 3 (coded value, I also couldn't find a ideal controlled terminology code for the utensil, we have fork, spoon, knife, glass, hand, chopstick).
For FHIR version, as the 3 records belongs to the same session. I use 4 components to store all the information (Datetime meal started and completed, datetime when type of utensil was recorded, and type of utensil been used).
"component": [
{
"code": {
"text": "meal started"
},
"valueDateTime": "2019-05-23T17:01:31+00:00"
},
{
"code": {
"text": "meal completed"
},
"valueDateTime": "2019-05-23T17:10:37+00:00"
},
{
"code": {
"text": "datetime, untensil used"
},
"valueDateTime": "2019-05-23T17:16:07+00:00"
},
{
"code": {
"text": "utensil"
},
"valueString": [
"3"
]
}
Lloyd McKenzie (Feb 11 2020 at 23:50):
Typically you're better to define your own code system than to use text. 'text' isn't considered computable - it's just for humans to look at. If you want other systems to recognize your data, you're going to want to have codes of some sort, even if the code system is one you define yourself.
Last updated: Apr 12 2022 at 19:14 UTC
