-
Notifications
You must be signed in to change notification settings - Fork 45
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
Cholesterol schema #7
Comments
Hello Tom and thank you for your message. You did not miss anything. There is currently no schema for cholesterol. We have not had a use case for such measure. Could you provide us information on the mHealth devices that are measuring cholesterol? |
There are few apps which allow to manual track your cholesterol (below) so I looked for a schema which relates to it - |
Thanks for the pointers. In all cases, the values are manually entered by the user via the app's UI. I will put your request in the request list. If you have an urgent need for the schema, our website has an annotated template and example to guide development of a quantitative schema http://www.openmhealth.org/documentation/#/schema-docs/write-a-schema/annotated-quantitative-measure-schema-template I will be happy to answer any questions you may have. |
Thank you Tom for your proposed schemas. I took a quick look and have some suggestions for amendments: 1. one of the sample data files refers to blood glucose; 2. I am not sure why you are importing specimen_source schema then adding again the values it already includes; 3. the description at the beginning of the cholesterol schema does not match its content (also, triglycerides are not a fraction of total cholesterol). I also recommend that you make effective_time_frame required in the schema. This is a change from the current template we are in the process of making and it is also something we have been doing in newly published schemas. |
I look for cholesterol related schema. I was not able to find anything. Did I miss anything? Is it planned?
The text was updated successfully, but these errors were encountered: