October 18, 2003

Imagine the uses of XML Schemas

One of the major discussions around this week is the separation of a web page style from the content contained within the page. Some believe this is possible, others don?t. I like to think it is. I?d like to find the time, to try an idea I have had. All the parts of the idea are coming together, but I?m going to share it. If you try it, please let me know how it works.

I think the idea of separating the information from the format of a document is a very powerful one. In a hospital setting this can be applied in many places the policies and procedures, the in-house formulary, nursing procedures, and the laboratory testing methods to name a few. If one could separate the information contained within these documents from the document authoring tool, imagine the possibilities.

For example, the in-house formulary is probably published in a booklet that medical students and residents rely upon. There hopefully is a web-based formulary, and a bunch of word documents where the pharmacy department can access. So there are many places to update, and many means to disperse the information.

The data needed for a drug or guideline is standardized. The pharmacists know what needs to be there and what doesn't. I'm proposing separating the data from the viewing tool. If the data is in an .xml file repository, and an XML Schema that defines the data elements necessary in the .xml file, then incorporate the XML schema into the viewing tool.

The advantage is one central location to update the data, and automatic dispersion of the data. All of the viewing tools are starting to incorporate xml schemas.

The disadvantages is that this is all conjecture. I haven't tried anything yet, need to get some new software approved, and time to play after work.

Posted by Elyse at October 18, 2003 7:42 PM