Thank you! From: [email protected] [mailto:[email protected]] On Behalf Of Paul (Google) Sent: Friday, June 25, 2010 6:45 PM To: [email protected] Subject: Re: [Google-Health-API] Description Element - Codes only vs. Codes and Text
Hi Peggy, Welcome to the Health developers' forum! If you have both codes and textual descriptions, it's best if you send both. Health will infer the names for entries sent with recognized codes but without textual descriptions. However, we presently don't have a service for determining which codes are supported. You can determine if a particular code is supported by creating an entry via the UI, and retrieving the CCR via the GData feed. If both text and a code are provided, the text is displayed in the UI. You should certainly send codes if you have them, even if Health presently doesn't support them. The Version element is presently optional and doesn't affect how the name of an entry is displayed in the UI. Thanks for the great questions! I hope the answers help. Paul (Google) On Fri, Jun 25, 2010 at 12:14 PM, Peggy <[email protected]<mailto:[email protected]>> wrote: We will be sending codes under the description element. We have text descriptions that we could also send. How does a description element with codes only vs. a description element with both codes and text impact what is displayed on the UI? The Google documentation says this, "The value from the description field is displayed in the 'Name' field on the Google Health UI. Set the 'Name' field by using the .../.../Description/Text element or by using a valid <Code> value. The later is recommend." In the CCR examples, both text and codes are included. Also, Version is a child under Description/Code. Is Version needed in the Google CCR? Does the need for this have any dependency on whether we send codes only vs. codes and text? -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]<mailto:[email protected]>. To unsubscribe from this group, send email to [email protected]<mailto:googlehealthdevelopers%[email protected]>. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en. The BLUEKC Mail System made the following annotations: -------------------------------------------------------------------------------- CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message. ======================================== -- You received this message because you are subscribed to the Google Groups "Google Health Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/googlehealthdevelopers?hl=en.
