Multiple agency data in an xml file
stevec
Looking at the 2.7 schema, is there a way to have an organization send
data representing multiple agencies with multiple programs within one
xml file? The database ID (upper level) would be the data warehouse
name. Then would come the next lower entity (a county), and under
this would be the agency name, then the specific programs, which would
have the client data associated with them.
So we would like to get a file from a county with multiple agencies
representing multiple programs and clients. Is this possible in the
schema and do vendors have experience with this? Thanks.
Steve Coretti
Safe Harbors
Eric Jahn
> Hi folks:
> Looking at the 2.7 schema, is there a way to have an organization send
> data representing multiple agencies with multiple programs within one
Hello Steve,
In 2.7 you can have one XML that has many SourceDatabase elements, each
with different DatabaseIDs, for each program. You'll have to assign a
different database ID to each program. You'll probably want to make a
document that tracks which DatabaseID corresponds to which program. The
XML won't declare your county/agency/program hierarchy, but the mapping
doc should keep everything straight. The receiving HMIS then can be
programmed to know that DatabaseID X corresponds to program Y which is
under agency Z (at County A). In 2.8, you can only transmit one
SourceDatabase, but you can have many DatabaseIDs with corresponding
client info. In an effort to flatten the schema SourceDatabase became
the root element in 2.8, so there could be only one, but the same
functionality of being able to submit many programs' data is there. The
best way, I think, for both 2.7 and 2.8, is to make a separate XML doc
for each DatabaseID, to keep the XML files as small as possible. When
messaging comes on board, we'll take this further, and just transmit
valid snippets (specific indexed subelements) of the HMIS XSD in a
message, or the whole doc. Hope this helps. -Eric
--
Eric Jahn
Alexandria Consulting LLC
3126 8th Ave. N
St. Petersburg, FL 33713
941.321.1466
skype: ejahn_
stevec
Steve
Brian Sokol
In 2.7 there is a Program complex element under the SourceDatabase .
Within Program there is both a ProgramID and ProgramParentID. The
ProgramParentID is intended to capture organizational hierarchies. You
can associate client encounters with any program you want under the
ProgramParticipation element by reference using the PPProgramID element.
In 2.8 the Program element is discontinued as it defers to AIRS to
represent all resource information and imports the AIRS schema. In AIRS
(and hence 2.8) what we call a program is called a "SiteService" . The
AIRS framework has a more comprehensive approach to representing
relationships among agencies, sites, services, etc.
Brian Sokol
Abt Associates Inc.
Phone: 617-349-2532
Fax: 617-386-7648
http://www.abtassociates.com
Eric Jahn
<eric@alexandriac
onsulting.com> To
Sent by: HMIS_Data_Integration@googlegroups.
HMIS_Data_Integra com
tion@googlegroups cc
.com
Subject
[HMIS Data Integration] Re:
06/24/2008 04:07 Multiple agency data in an xml file
PM
Please respond to
HMIS_Data_Integra
tion@googlegroups
.com
-----------------------------------------
This message may contain privileged and confidential information intended
solely for the addressee. Please do not read, disseminate or copy it unless
you are the intended recipient. If this message has been received in
error, we kindly ask that you notify the sender immediately by return email
and delete all copies of the message from your system. Thank you.