-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Static Measurements #12
Comments
I find this a good suggestion as it allows users to have it "both ways". |
It would be good to document the [edit: other] options that we've considered here. I think these include: 1. Events with a null timestamp are considered "static events".
2. Add
|
What about the approach in the former screenshot; just have |
Sorry, the options that I listed were intended to be "other options". |
Ahh, makes more sense, sounds good.
…On Thu, Feb 15, 2024, 12:08 PM Tom Pollard ***@***.***> wrote:
Sorry, the options that I listed were intended to be "other options".
—
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADS5XZB7U62L7WQKT34UUTYTY6JLAVCNFSM6AAAAABDGYUD52VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBWGYYTMMRYGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I kind of like option 3 (the metadata option), though I think at some point there was a metadata field on the measurements schema? If this is still there, it would get confusing. |
For simplicity I think the prior approach (just have |
Ok, vote cast on Slack! |
I recommend we move static measurements as a separate measurements list within patients, rather than relying on them within events.
This would make the schema look more like it did originally, like this:
This
static_measurements
field would reflect variables recorded at a per-patient level in the data without a timestamp. This makes it easier to do any temporal operations on the data, better reflects the conceptual division of data in the dataset, and it is trivial to transform the data to put static measurements into an event if that is preferred by a modeler.The text was updated successfully, but these errors were encountered: