Part of our application will take data from the CCR and present it in
a human-readable form. I have looked through the API documentation,
specifically http://code.google.com/apis/health/ccrg_reference.html
and the ccr_example.xml file, as well as the screen-shots showing the
Google Health UI. However, I still have some uncertainty how data will
be made available.

First - for Problems, Alerts and Procedures there is a Description
element. For Medications and Immunizations there is a ProductName
element. Within those, there can be a Text element - a human-readable
name, and also a Code element holding Value and CodingSystem elements.
I am not sure I can count on a Text element being there. In the ccr-
example file, there are several that don't have the text. For those, I
would have to do a look-up in the coding system. Am I wrong to think
that Google would already have done that lookup and provide the
relevant text element?

Second - in the documentation and ccr-example, data is named problems
and alerts. However, in the UI, that data is named Conditions and
Allergies. Are there alerts that are not Allergies, and similarly, are
there problems that are not Conditions?

Third- the UI screens-shots show user-entered for some data and
another source for other data. I can't see where in XML that is
defined and it doesn't show up in the ccr_example file. What should I
be looking for?

Fourth - for a medication, if it is a prescription, what data can I
count on being there and how can I detect that this is a prescription
rather than an OTC medication. As an example, would a prescription
always have a prescription ID?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to