The short answer is no, not in general. Or at least not without more help from your insurance company. That said, you could try
Liquid XML, which offers tree- and table-based views of XML documents. (Haven't used it myself, but it looks reasonable.)
Why not?
Because there's no correct way to display an XML document. XML documents will contain a number of elements, comprising tags (the code bits you're seeing) and content (the bit you actually want). Here's an example from Wikipedia:
Code:
<?xml version="1.0" encoding='ISO-8859-1'?>
<painting>
<img src="madonna.jpg" alt='Foligno Madonna, by Raphael'/>
<caption>This is Raphael's "Foligno" Madonna, painted
in <date>1511</date>-<date>1512</date>.</caption>
</painting>
It's possible to specify a schema for the document, which specifies which elements can be used where. For instance, this page is supposed to meet the XHTML 1.0 Transitional DTD (schema),
defined here. There's a line at the top of the page that states this
Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
Your document will probably have a similar line at the top, presumably referencing a schema created by your insurance company.
The difference between this page and the document you have is that your browser knows how to display XHTML pages (because this is well defined by rules and convention). The same is true for Office 2007 files, which are XML files that meet Microsoft's schemata.
Whereas your document could contain anything (within its schema). It may make sense to show certain parts of it in a table, or a list, but it may not. And it's not really something that can be inferred, beyond the 'suck it and see' table / tree approach, without additional domain knowledge.
Basically, your insurance company shouldn't have sent you that file. It's designed for machines to read (machines that have access to the schema), not you. They should have sent you a PDF instead.