Remove the Ontology

Registered by Tim Cook

The 2 purposes of the Ontology are to allow translations of strings and to allow enumeration of options for a specific entry. Since XML datatypes carry an enumeration facet this is not needed in the Ontology now. In order to accurately develop and maintain translations there is a lot of extra tool knowledge required of modelers. I propose that translations should be done on a CDD file (mindmap) and that translation creates a new CCD. This approach does not provide for immediate translation within an application of one CCD though. For example, a body weight CCD in English will be a different CCD than a body weight CCD in Portuguese or Dutch. But is this a serious issue? The CCD instance would still be usable across systems but there would not be language translation. Removing the Ontology greatly reduces the complexity of CCDs. Elements will be added to the MLHIM Meta-Data set in order to track back to the original CCD. OR XML Schemas allow for substitution groups that can handle translations. So in stead of creating a new CCD, it could be translated as the schema (CCD). This could make for some very complex CCDs though. Thoughts?

RE 17-6-2011:
I don't get what you mean with the substitution groups and the subsequent sentence, probably due to my lacking XML (Schema) knowledge. But maybe another possibility is to have something alike a Terminology Service: a Translation Service. Depending on the system-wide locale or one configured in the health care application, a corresponding translation can get obtained from that service. It seems to me that this way you need just one, not too complex, CCD.

Blueprint information

Status:
Complete
Approver:
Tim Cook
Priority:
High
Drafter:
Tim Cook
Direction:
Approved
Assignee:
MLHIM Specifications Developers
Definition:
Approved
Series goal:
Accepted for 2.0
Implementation:
Implemented
Milestone target:
milestone icon 2.3.0
Started by
Tim Cook
Completed by
Tim Cook

Related branches

Sprints

Whiteboard

Also removed the OntologyEntry class.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.