Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
R4
-
Modeling & Methodology
-
Datatypes
-
2.24.0.11
-
-
Lloyd McKenzie / Jose Costa-Teixeira: 8-0-0
-
Enhancement
-
Compatible, substantive
-
R5
Description
SampledData assumes the sampling period is consistent, which makes it unsuitable for data with a variable sampling period.
One way to solve this is suggested by GrahameGrieve:
> we could add a new element offsets : string that has the same format as data, and specifies the instants at which measurements were made. In this scheme, period is redefined as the default offset increment for any data point that runs off the end of the array of offsets. That's procedurally possible, and the least worst way to handle sampled data that doesn't have regular time intervals
Example of how this would look like:
"valueSampledData": {
"origin": {
"value": 0,
"code": "deg",
"unit": "degree",
"system": "http://unitsofmeasure.org",
{{ },}}
"period": 1000, // semantically does not mean anything, only here for the 1..1 cardinality
"dimensions": 1,
"data": "47.53885435017747 90.00021045865756 90.00021045865756",
"offsets": "3378.787878787879 3421.053306 5921.053306"
}
(zulip thread - https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Representing.20array.20of.20data.20with.20variable.20timing)
Attachments
Issue Links
- mentioned in
-
Page Loading...