← Back to team overview

oship-dev team mailing list archive

Re: CDD Questions

 

Hi OSHIP-Dev,

Tim, Sergio and I have been discussing this in presential meetings over the last weeks. I think we are reaching to an agreement about this part of the MLHIM specifications. But it would be *excellent* to hearing somebody else's opinions, especially from those who are knowledgeable about XML, regardless their level of skills on the openEHR/MLHIM specifications. Some creative ideas could emerge from that.

Cheers, Luciana.


Tim Cook escreveu:
Hi Justin,
I have copied this to the OSHIP-dev list so that others may benefit from the conversation.

On Thu, May 6, 2010 at 9:33 AM, Roberto Siqueira <siqueira@xxxxxxxxxxxxxxx <mailto:siqueira@xxxxxxxxxxxxxxx>> wrote:

    Hi all:
     Let me try to address the "XMLSpy" part:

    > - why can't XML spy be used? (or similar xml editor) - there are
    > existing tools to build xml files from xsd files. Converting the xsd
    > files to Glade widget is basically converting xsd to xml - since
    glade
    > is an xml in its entirety.

     You're perfectly right [in fact, that's precisely the reason why
    moving from ADL to XML was a big step forward: we don't need to
    "reinvent the wheel" any more]. There are even XSD-aware,
    context-sensitive editors like Oxygen
    ( http://www.oxygenxml.com/intelligent_xml_editing.html ) and
    Serna Free
    ( http://www.syntext.com/products/serna/features/xml-validation/
    ), that
    are *very* user-friendly.
     But you must remember that our main users are MDs (medicine doctors),
    not ITs (information technologists). On the long run, some of them
    will
    get well acquainted with the XML tools, but most of them will
    rather use
    something like http://www.phpform.org/ (by the way, the nicest "form
    buider" I've found so far!) instead. Indeed, that's is the main
    paradigm
    of this 2-tier project: to separate the medical knowledge "layer" from
    the IT one, so each specialist can concentrate only on his/her own
    domain.

I'm not certain that I was clear in past emails about the use of XML Schemas as concept constraint definitions (CCDs), aka. archetypes in openEHR and in template constraint definitions (TCDs), aka. Templates in openEHR. Both the CCD and TCD should be represented as an XML Schema NOT just an XML file. Remeber that an 'archetype' does not contain data. It is a defining framework for data. The 'instance' of an archetype is similar to an XML file. These contain data and must validate against the archetype/template or CCD/TCD respectively. So, for CCD and TCD schemas; they will 'include' the XML schemas of the reference model and then define the clinical concept (CCD) or a group of clinical concepts (TCD). Comments? / Suggestions? Tim

--
Esta mensagem foi verificada pelo sistema de antiv�rus e
acredita-se estar livre de perigo.
------------------------------------------------------------------------

_______________________________________________
Mailing list: https://launchpad.net/~oship-dev
Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~oship-dev
More help   : https://help.launchpad.net/ListHelp

--
Esta mensagem foi verificada pelo sistema de antiv�s e
acredita-se estar livre de perigo.


References