On Dec 11, 5:01 pm, "Renda, Michael" <michael.re...@makeready.com>
wrote:
> Eric,
>
> Thanks for the information. I have a couple of questions.
>
> 1. What specifically was wrong with the CCR that I sent?
I think the extra meta data was the issue, but to be sure register/ui
feed would tell you.
I was able to POST this:
<?xml version="1.0" encoding="UTF-8"?>
<atom:entry xmlns:atom="http://www.w3.org/2005/Atom";>
<atom:title type="text">test</atom:title>
<atom:content type="text">here</atom:content>
<category term='CONDITION' />
<title type='text'></title>
<ContinuityOfCareRecord xmlns='urn:astm-org:CCR'>
<Language />
<DateTime>
<Type />
</DateTime>
<Body>
<Problems>
<Problem>
<DateTime>
<Type>
<Text>Start date</Text>
</Type>
<ExactDateTime>2008-12-04</ExactDateTime>
</DateTime>
<DateTime>
<Type>
<Text>Stop date</Text>
</Type>
<ExactDateTime>2008-12-04</ExactDateTime>
</DateTime>
<Type />
<Description>
<Text>Bowel Movements</Text>
</Description>
<Status>
<Text>ACTIVE</Text>
</Status>
</Problem>
</Problems>
</Body>
</ContinuityOfCareRecord>
</atom:entry>
> 2. Can you use /register/ui with a token obtained through ClientLogin?
Yes. The permitted HTTP operations are here:
http://code.google.com/apis/health/docs/2.0/reference.html#Authentication
>
> Thanks,
>
> Mike
>
> On 12/11/08 7:48 PM, "Eric (Google)" <api.e...@google.com> wrote:
>
> I can confirm that POSTing invalid CCR to the /profile/ui feed
> renders the profile unreadable via the API. At the moment, I'm not
> sure how
> regain access to the profile. This is definitely a bug and we'll look
> into this ASAP.
>
> In the future, you should really be sending CCR via the /register/ui.
> That feed
> has a system to reconcile CCR data. If it is invalid data, the
> profile remains
> untouched.
>
> Please file a bug here:http://code.google.com/p/gdata-issues/issues/entry
>
> Thanks!
> Eric
>
> On Dec 11, 1:36 pm, "Renda, Michael" <michael.re...@makeready.com>
> wrote:
>
>
>
> > I can post code, but (fair warning) it's objective-C - an iPhone
> > application. Do you still want it?
>
> > Other than that, I can send you the XML I get from the Profile list request
> > and the log output from various program variables.
>
> > Mike
>
> > On 12/11/08 4:34 PM, "Eric (Google)" <api.e...@google.com> wrote:
>
> > Can you post the code so I can try to reproduce?
>
> > Eric
>
> > On Dec 11, 5:52 am, "Mr. Creosote" <michael.re...@makeready.com>
> > wrote:
>
> > > I've built a simple test app to test various api elements and to get
> > > direct examples of the xml formats.
>
> > > The app:
>
> > > 1. Authenticates using ClientLogin
> > > 2. Gets a profile list
> > > 3. Retrieves the first (and only) profile in the list
> > > 4. Updates the patient's weight
>
> > > This has all been working just fine. But this morning it stopped
> > > working.
>
> > > I can authenticate and get the profile list. But when I attempt to
> > > read the profile I get a response code 404 Not Found.
>
> > > I didn't change any code - I don't think. Looking at the profile list
> > > response, I can see the proper 'id' being returned. My app is
> > > correctly parsing that id and properly forming the url for a profile
> > > request. There doesn't seem to be a problem with the authentication
> > > token (I am able to retrieve the profile list after all).
>
> > > Is there some problem with the site? By the way, I'm
> > > usinghttps://www.google.com/health, not h9.
>
> > ________________________________
> > Michael Renda
> > President
> > makeReady Systems, Inc.
> > 88 East Main Street, Suite 330
> > Mendham, New Jersey 07945
>
> > ( Phone (973) 796-2750
> > * Fax (973) 796-2663
> > È Cellular (973) 769-2427
> > * eMail michael.re...@makeready.com
>
> ________________________________
> Michael Renda
> President
> makeReady Systems, Inc.
> 88 East Main Street, Suite 330
> Mendham, New Jersey 07945
>
> ( Phone (973) 796-2750
> * Fax (973) 796-2663
> È Cellular (973) 769-2427
> * eMail michael.re...@makeready.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Health Developers" group.
To post to this group, send email to googlehealthdevelopers@googlegroups.com
To unsubscribe from this group, send email to
googlehealthdevelopers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/googlehealthdevelopers?hl=en
-~----------~----~----~----~------~----~------~--~---
