Dear all, I am not sure whether this is premature but I curious as to which part of an OpenEHR compliant EHR-S will enforce the constraints that are embedded in an archetype model - I note the use of the term data validator on the web site - Will the kernel in an OpenEHR server parse data (for instance to assess completeness of a communicated extract) using some sort of constraint processor - or will this be up to individual implementers to sort out?
Also, is there any ongoing implementation / validation work on how to map archetype-based communications into (for instance) decision support services? Will it be practical to incorporate legacy DSS systems or will it be necessary that a DSS function within an OpenEHR-compliant EHR-S is built from scratch around the OpenEHR models? Finally - how would you go about developing an OpenEHR-compatible instrument interface? What steps would be taken in order to feed "raw" measurements from an instrument into the EHR? I suspect that this would involve some of the following activities. I would like your guidance on how the scenario continues, and/or whether it is in the scope of the work. AT DESIGN / IMPLEMENTATION TIME DOMAIN SPECIALISTS AND DEVELOPERS... - create an archtype with the appropriate constraints to comply with data provenance, context requirements etc. - implement an instrument interface that produces (in cooperation with an OpenEHR server) the minumum set of data surrounding the measurement that is required by the archetype AT RUN TIME THE INTERFACE... - constructs a message including all of the context information (time stamp, origin,etc) surrounding the raw measurement - checks for completeness of the data - facilitates(?) a check for correctness of the data - ?? - passes the information to the EHR-S where it is incorporated into the EHR (automatically? or only with "signed" human consent?) Best Regards, Damon Berry -- This message has been scanned for content and viruses by the DIT Information Services MailScanner Service, and is believed to be clean. http://www.dit.ie - If you have any questions about using this list, please send a message to d.lloyd at openehr.org