|
XML PowerPoint - Kickoff Presentation for cwXML /
ICPC Effort
View PowerPoint Presentation
Developing XML Standards for Child Welfare
Using the ICPC Process as a Model and a Starting Point
October 10, 2002
Agenda
- Introductions
- Meeting Goals and Objectives
- The ICPC Business Process
- XML Defined
- Developing XML Standards
- ICPC SOAP Exchange
- Identifying Tasks, Timeframes, and Responsibilities
- Next Steps
Objectives
- Develop the national XML standards for child welfare (using
the ICPC process as a model and a starting point)
- Develop these standards by November 2002 (6 weeks!)
- Capitalize on the knowledge and expertise of the public/private
partnership
ICPC Model
| Sending State |
|
Receiving State |
| Request Placement |
| 100A |
 |
|
| |
 |
100A |
| Approve/Deny
Placement Request |
 |
| |
| 100B |
Place Child |
|
| |
|
|
| 100B |
Change/Terminate Placement |
| |
|
|
XML Is:
- A set of standards for annotating or “tagging” information
so that it can be transmitted over a network and readily
interpreted by disparate computer systems. For example:
Johnny Smith
- A method to have a computer generate data, read data,
and ensure that the data structure is unambiguous
- Extensible and platform-independent: data and business
processes can be shared throughout and between organizations
regardless of technologies used
XML Is Not:
XML is important because it’s:
- Easy to deploy
- Easy to read and understand (need to encrypt data transmissions
for security concerns)
- Becoming the standard way to identify, describe, and exchange
data over the Internet and other networks
How is it being used?
- Exchanging legal information between courts and child
support agencies
- Exchanging public health eligibility and enrollment information
- Exchanging case management information across various
locations and organizations with a legal interest
Sources of Information: www.w3.org and
SITC
XML Standards:
- Technical: have largely been worked out by commercial
standards-setting organizations
- Business: are not as mature and can complicate implementations
- Identifying potential business partners for transactions
- Exchanging precise technical information about the nature
of proposed transactions so that the partners can agree
to them and integrate them into existing systems
- Executing agreed-upon transactions in a formal, legally
binding manner
Our Imperative:
- To develop XML standards within a communication protocol
that can be easily implemented and reused by all child welfare
agencies
ICPC SOAP Exchange
| Sending
State |
|
Receiving
State |
| 1. User defines client and form type |
6. Adaptor receives XML file |
| 3. User specifies recipient State |
7. Adaptor maps and validates data |
| 4. Adaptor automatically determines
recipient transfer method (HTTP, FTP, SMTP) |
8. Adaptor prepares data
for loading: 1) real-time load into RDBMS, 2) Generation
of Text/CVS file, or 3) Generation of Form Summary for
printout |
| 2. Adaptor generates XML file |
| 5. Adaptor initiates XML file transfer
from SOAP node |
ICPC SOAP Exchange
| ADAPTOR |
| Form
Send |
| |
Transfer Specification
(Client/Form Recipient) |
|
| Database Connector |
| XML File Mapping (Send) |
| XML Standard File Generation(Send) |
| Form
Receive |
| |
XML File Mapping (Receipt) |
|
| Database Connector |
| Data Output |
| Administration |
| |
Mapping Configuration |
|
| Connectivity Configuration |
| Output Configuration |
| Address Book |
| Security |
Identifying Tasks, Timeframes, and Responsibilities
Two Work Groups:
I. Development Group – role is to:
- Define the XML standards
- Determine how XML will be implemented for the ICPC process
- Develop the technical exchange of data
- Share knowledge: documentation, training and learning
exercises, etc.
II. Management Group – role is to:
- Get XML standards approved
- Register XML standards
- Communicate status of this undertaking to interested parties
(i.e. ACF, SACWIS Users Group)
- Update XML web site (www.nrcitcw.org/xml/intro.html)
Next Steps
Six Weeks to XML
- Weekly Conference Calls - every Thursday starting 10/17/2002
- Status update from each work group
- Detailed workplans from each work group should be provided
- Update to SACWIS Users Group on November 22nd SACWIS Conference
Call
| 
