Thomas, I agree.
I creatively used the term "state" and "state machine". Your suggestion " lifecycle state" is much better. Whether openEHR and EN13606 model the "lifecycle state of data and information in documents model this explicitly might be true. But implictly it does. My question for you are: - Do we have to make this explicit? - Will this be using tables in EN13606 part 3 and openEHR? - Will this be using Archetype families? - other ways? Gerard -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 653 108732 On 14-mei-2006, at 2:39, Thomas Beale wrote: > Gerard Freriks wrote: >> Hi Sam, >> >> The EHR-system cannot function without State models. >> There will be archetypes that contain state models. >> Because they are expressions of business rules and other domain >> knowledge. >> Therefor the Archetype Ontology will have at least one State Model. >> >> The EHR will contain a (implicit?) State Model! >> (This is to the contrary of what I have written in a recent e-mail) > To keep things clear, I suggest we use the terminology "lifecycle > state", i.e. of the documentation in the EHR; otherwise we tend to > use "state" and "state machine" to refer to the state of an > Instruction as it is executed in the real world (e.g. started, > cancelled, postponed, active, suspended, aborted, completed etc). >> >> This State Model, that is part of the EHR (and should be of >> EN13606 part 1) deals with topics like the states data, >> information and knowledge can have in the process of recording: >> - raw data received - rejected - ... >> - raw data admitted/committed to the EHR - rejected - ... >> - information (processed data + professional opinion) - ... >> - report (selected information by a professional) - ... >> - report sent > openEHR doesn't model all of these, but some are modelled in > VERSION.lifecycle_state; others are lower-level concepts in the > communications framework.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20060514/b502f38d/attachment.html>
