On 20-02-18 20:09, Thomas Beale wrote:
The terminology service also has dependencies to rm data types, only
because of codephrase. Wouldn't it be possible to avoid that?
Yes, there is a new class TERMINOLOGY_CODE that is used in BASE
instead of CODE_PHRASE; eventually, the RM should just use that. If
you found any use of CODE_PHRASE in BASE, please let us know.
This is of course a good thing.
But now the question, how do I know which definition to use.
I always looked at this URL:
http://www.openehr.org/programs/specification/workingbaseline
There I found "Support", which brings me to:
http://www.openehr.org/releases/RM/latest/docs/support/support.html
In that, there is CODE_PHRASE still used in TERMINOLOGY_ACCESS.
Now I read that there is a new class in BASE, I found the link:
http://www.openehr.org/releases/BASE/latest/docs/index
And I found Terminology_Code:
http://www.openehr.org/releases/BASE/latest/docs/base_types/base_types.html#_terminology_code_class
Which is a real improvement, exactly what I was hoping for, it did not
only remove the CODE_PHRASE from datatypes, but also TERMINOLOGY_ID
class from SUPPORT
It has a property/field which is named terminology_id and is of type string
Is this what is going to be the new standard?
And when will this be like that?
When looking further, I also see that there is still a TERMINOLOGY_ID
class in that document which is the old support terminology which is
derived from OBJECT_ID
http://www.openehr.org/releases/BASE/latest/docs/base_types/base_types.html#_terminology_id_class
Is this confusing, or am I missing something stupid? Am I the only
person asking this kind of questions? If yes, where do others get their
information from?
Please help me, because, I think, this is very important.
Thanks
Bert
_______________________________________________
openEHR-technical mailing list
[email protected]
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
