This area is designed to help you transition to the new Web Services with as few problems as possible. Here we will go over what has changed and discuss some of the issues that you may run into.

XML Structure Changes

In order to support more content types it was necessary to overhaul the existing XML structure. In doing so we have allowed room to grow within the structure so we will not have to make as many significant changes in future releases. Below is a list of changes to be aware of when migrating to the new methods.

• Please note that these changes only apply to the new methods in the Content service. The old methods will continue to work as they always have, until they are removed.
• The new methods do not use Staywell namespaces. This should simplify any XPath queries you use to parse our XML.
• There is no longer a "NonValidBody" element to indicate if the body should be transformed or not, the element will always be named "body". The "IsValid" attribute of the ContentObject element should be used to determine if the XML needs to be transformed or not.
• We have changed all attributes and elements to be PascalCase (each word has an inital caps), with the exception of ICD9, CTP and MeSH.
• All new web service results use our new xml schema, see the Content API section for more details about changes to individual methods.
• We have updated the validation of all XML used by the new methods, including the XmlRequest value used to send parameters. This means that datatypes will be validated against the W3 standard. For example, the W3 bool datatype is defined as "true" or "false" so if you pass in "True" you will get an error message stating "The string 'True' is not a valid Boolean value."
• Attribute change: "IncludeOriginalDocuments" is now "GetOriginal".
• Attribute change: "IncludeDocuments" is now "IncludeContent".