Draft HMIS REST API

[Eric Jahn]

All,
I've worked up a draft REST messaging API. It's at:
http://tinyurl.com/58mu89 The accesskey parameter especially needs to
be discussed more, but I also wanted to get your overall feedback on
this draft API. A test messaging server you will be able to send
messages to is the next step after we improve this API. Thanks! -Eric

--
Eric Jahn
Alexandria Consulting LLC
3126 8th Ave. N
St. Petersburg, FL 33713
941.321.1466
skype: ejahn_

[David Talbot]

I'd recommend consolidating the Create/Updates. Make the system receiving
the data decide whether it's a new record or an existing one for them. The
system receiving the data is going to want to "protect" itself from possible
garbage data anyway (IE, if you send me a create, I'm going to ignore it and
check to see if it already exists anyway.)

Although the source system/dest system obviously have different
clientids/serviceids etc its important to pass them especially in real time
integration. IE, if you send me a service record for "Bag o' Food" then send
me an identical record 10 seconds later, my system has to decide to drop it
as a dupe (the result of a re-transmission) or post it as a real. Since I
track all of the serviceIDs you've provided to me I'd know.

-David Talbot
VP of Development
ClientTrack

[Eric Jahn]

David,
Both your ideas make sense. I'll make those changes and repost the API
in the same place. -Eric