Dear William, There are State Machines and "state machines". They serve a business purpose. So before we know what we are talking about we must know the context.
I was talking about the state one's and zero's in strings go through going from data, to information expressing a professional opinion. data in -> information and knowledge out. Of course there are state machines for: messages, clinical workflow office workflow, etc, etc Can you provide us the context of the State Machines HL7v3 provides at this moment? Gerard In the proposed part 3 of EN13606 there is the following text about possible states an Entry in EN13606-1 EHRcom can have. ENTRY.act_status ACT01 Foreseen ACT02 Requested ACT03 Accepted ACT04 Booked ACT05 Planned ACT06 Ready ACT07 In progress ACT08 Completed ACT09 Reported ACT10 Terminated ACT11 Forwarded ACT12 Suspended ACT13 Annulled-Cancelled ACT14 Annulled-Rejected ACT15 Substituted NOTES: These terms are identical to those in HISA, as previously discussed and agreed, except that codes have been added. HISA will relate these as appropriate to HL7 Mood Codes. The original ENV13606 Domain Termlists for life-cycle and process status have been removed in favour of this more rigourous and harmonised list. -- <private> -- Gerard Freriks, arts Huigsloterdijk 378 2158 LR Buitenkaag The Netherlands T: +31 252 544896 M: +31 653 108732 On 12-mei-2006, at 14:40, Williamtfgoossen at cs.com wrote: > In een bericht met de datum 12-5-2006 13:42:29 West-Europa > (zomertijd), schrijft gfrer at luna.nl: > > >> >> 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) > > > As sais before, the HL7 state machine is based on years of > experience, and if we talk about harmonizing, these are exactly the > items that would apply in CEN 13606. > Then the lacking items in OpenEHR can be enhanced too. This state > machine operates on Act, which can be any clinical EHR entry, and > you could limit the Act attributes if you want (except the status > code of course, because that is what you need). > > William -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-clinical_lists.openehr.org/attachments/20060512/0e337322/attachment.html>
