HL7 and HCLS - Revision history

Phismith at 14:08, 6 October 2013

2013-10-06T14:08:42Z

@@ Line 21: / Line 21: @@
 :In this case restriction is applied on the Entity class. Please note that in addition to this restriction definition, first the classCode needs to described as an object property with a domain: Entity class and Range: CS class. For the second option, thanks to OWL 2 for allowing restrictions (i.e., minimum and maximum cardinality) on properties definition as below[.]
+HL7 and HCLS are both volunteer efforts comprising people with good intentions who wish to advance the use and sophistication of information technology in clinical domains. When HL7 representatives volunteered to contribute to the work of HCLS they were, accordingly, warmly greeted – not least given the fact that the HL7 community has been for some time itself talking of its standards as contributing to what they called 'semantic interoperability'.
 For W3C talk of the ‘semantic interoperability’ of independent information systems signifies that these systems are able to exchange, correctly interpret, reuse and aggregate data. This is achieved by formalizing information to be exchanged using semantically well-defined languages such as RDF or OWL. "Semantics" here refers to traditional, model-theoretic semantics, as originally conceived by [http://www.hackettpublishing.com/philosophy/logic-semantics-metamathematics Alfred Tarski], and as utilized in ‘semantic technology’ for instance [https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html here]. (For background see [http://en.wikipedia.org/wiki/Semantics_(computer_science) here]. It is on this basis that the inferential and computational properties of OWL are defined -- just those properties which are widely held to lend significance to the work of W3C within the framework of HCLS and similar initiatives.)
 For HL7, in contrast, 'semantic interoperability' is something that is to be achieved by having multiple IT systems use (or be mapped) to a common reference information model called HL7 RIM. Several groups have attempted to create ontological representations of the RIM, but – for reasons discussed extensively on this [http://hl7-watch.blogspot.com/ blog] – such attempts have failed, because the RIM has no consistent documentation.

Phismith at 17:51, 23 August 2013

2013-08-23T17:51:16Z

← Older revision		Revision as of 17:51, 23 August 2013
Line 1:		Line 1:
	The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN)] and [http://neurocommons.org/page/Main_Page Neurocommons] projects.		The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN)] and [http://neurocommons.org/page/Main_Page Neurocommons] projects.

	Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully vetted by both domain experts and by those with expertise in logical model theory and in Semantic Technology.		Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully vetted by both domain experts and by those with expertise in logical model theory and in its application in Semantic Technology.

	Recently, however, HCLS has taken a strange turn, which is illustrated here:		Recently, however, HCLS has taken a strange turn, which is illustrated here:

Phismith at 17:50, 23 August 2013

2013-08-23T17:50:46Z

← Older revision		Revision as of 17:50, 23 August 2013
Line 1:		Line 1:
	The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN)] and [http://neurocommons.org/page/Main_Page Neurocommons] projects.		The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN)] and [http://neurocommons.org/page/Main_Page Neurocommons] projects.

	Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully ~~proofread~~ by both domain experts and by those with expertise in ~~logic~~ and ~~ontology, including people able to write coherent English~~.		Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully vetted by both domain experts and by those with expertise in logical model theory and in Semantic Technology.

	Recently, however, HCLS has taken a strange turn, which is illustrated here:		Recently, however, HCLS has taken a strange turn, which is illustrated here:

Phismith at 17:49, 23 August 2013

2013-08-23T17:49:25Z

← Older revision		Revision as of 17:49, 23 August 2013
Line 24:		Line 24:
	In sum, it seems that -- like so many other promising initiatives in medical IT -- HCLS has been taken over, at least in part, by the HL7 monster. I believe that the explanation for how this takeover could have occurred goes something like this. HL7 and HCLS are both volunteer efforts comprising people with good intentions who wish to advance the use and sophistication of information technology in clinical domains. When HL7 representatives volunteered to contribute to the work of HCLS they were, accordingly, greeted with open arms – not least given the fact that the HL7 community has been for some time itself talking of its standards as contributing to what they called 'semantic interoperability'.		In sum, it seems that -- like so many other promising initiatives in medical IT -- HCLS has been taken over, at least in part, by the HL7 monster. I believe that the explanation for how this takeover could have occurred goes something like this. HL7 and HCLS are both volunteer efforts comprising people with good intentions who wish to advance the use and sophistication of information technology in clinical domains. When HL7 representatives volunteered to contribute to the work of HCLS they were, accordingly, greeted with open arms – not least given the fact that the HL7 community has been for some time itself talking of its standards as contributing to what they called 'semantic interoperability'.

	For W3C talk of the ‘semantic interoperability’ of independent information systems signifies that these systems are able to exchange, correctly interpret, reuse and aggregate data. This is achieved by formalizing information to be exchanged using semantically well-defined languages such as RDF or OWL. "Semantics" here refers to traditional, model-theoretic semantics, as originally conceived by [http://www.hackettpublishing.com/philosophy/logic-semantics-metamathematics Alfred Tarski], and as utilized in ‘semantic technology’ for instance [https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html here]. (For background see [http://en.wikipedia.org/wiki/Semantics_(computer_science) here]. It is on this basis that the inferential and computational properties of OWL are defined -- just those properties which are widely held to lend significance to the work of W3C within the framework of HCLS and similar initiatives.		For W3C talk of the ‘semantic interoperability’ of independent information systems signifies that these systems are able to exchange, correctly interpret, reuse and aggregate data. This is achieved by formalizing information to be exchanged using semantically well-defined languages such as RDF or OWL. "Semantics" here refers to traditional, model-theoretic semantics, as originally conceived by [http://www.hackettpublishing.com/philosophy/logic-semantics-metamathematics Alfred Tarski], and as utilized in ‘semantic technology’ for instance [https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html here]. (For background see [http://en.wikipedia.org/wiki/Semantics_(computer_science) here]. It is on this basis that the inferential and computational properties of OWL are defined -- just those properties which are widely held to lend significance to the work of W3C within the framework of HCLS and similar initiatives.)

	For HL7, in contrast, 'semantic interoperability' is something that is to be achieved by having multiple IT systems use (or be mapped) to a common reference information model called HL7 RIM. Several groups have attempted to create ontological representations of the RIM, but – for reasons discussed extensively on this [http://hl7-watch.blogspot.com/ blog] – such attempts have failed, because the RIM has no consistent documentation.		For HL7, in contrast, 'semantic interoperability' is something that is to be achieved by having multiple IT systems use (or be mapped) to a common reference information model called HL7 RIM. Several groups have attempted to create ontological representations of the RIM, but – for reasons discussed extensively on this [http://hl7-watch.blogspot.com/ blog] – such attempts have failed, because the RIM has no consistent documentation.

Phismith at 17:48, 23 August 2013

2013-08-23T17:48:17Z

← Older revision		Revision as of 17:48, 23 August 2013
Line 10:		Line 10:

	1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo		1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo
			:Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.
	Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.

	2. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/HL7_RIM		2. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/HL7_RIM
			:OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:
	OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:

	:Class: Entity		::Class: Entity
	:SubClassOf:		::SubClassOf:
	:entity.classCode max 1 CS, entity.classCode min 1 CS		::entity.classCode max 1 CS, entity.classCode min 1 CS

	In this case restriction is applied on the Entity class. Please note that in addition to this restriction definition, first the classCode needs to described as an object property with a domain: Entity class and Range: CS class. For the second option, thanks to OWL 2 for allowing restrictions (i.e., minimum and maximum cardinality) on properties definition as below[.]		:In this case restriction is applied on the Entity class. Please note that in addition to this restriction definition, first the classCode needs to described as an object property with a domain: Entity class and Range: CS class. For the second option, thanks to OWL 2 for allowing restrictions (i.e., minimum and maximum cardinality) on properties definition as below[.]

Phismith at 17:46, 23 August 2013

2013-08-23T17:46:21Z

← Older revision		Revision as of 17:46, 23 August 2013
Line 10:		Line 10:

	1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo		1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo

	Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.		Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.

	2. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/HL7_RIM		2. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/HL7_RIM

	OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:		OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:

Phismith at 17:45, 23 August 2013

2013-08-23T17:45:42Z

← Older revision		Revision as of 17:45, 23 August 2013
Line 1:		Line 1:
	The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN) and [http://neurocommons.org/page/Main_Page Neurocommons] projects.		The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN)] and [http://neurocommons.org/page/Main_Page Neurocommons] projects.

	Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully proofread by both domain experts and by those with expertise in logic and ontology, including people able to write coherent English.		Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully proofread by both domain experts and by those with expertise in logic and ontology, including people able to write coherent English.
Line 7:		Line 7:
	http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability		http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability

	Some samples, selected at random:		Some samples, selected at random (punctuation and syntax as in the original):

	1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo		1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo
Line 15:		Line 15:
	OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:		OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:

	Class: Entity		:Class: Entity
	SubClassOf:		:SubClassOf:
	entity.classCode max 1 CS, entity.classCode min 1 CS		:entity.classCode max 1 CS, entity.classCode min 1 CS

	In this case restriction is applied on the Entity class. Please note that in addition to this restriction definition, first the classCode needs to described as an object property with a domain: Entity class and Range: CS class. For the second option, thanks to OWL 2 for allowing restrictions (i.e., minimum and maximum cardinality) on properties definition as below[.]		In this case restriction is applied on the Entity class. Please note that in addition to this restriction definition, first the classCode needs to described as an object property with a domain: Entity class and Range: CS class. For the second option, thanks to OWL 2 for allowing restrictions (i.e., minimum and maximum cardinality) on properties definition as below[.]

Phismith: Created page with 'The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and...'

2013-08-23T17:42:35Z

Created page with 'The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and...'

New page

The Semantic Web Health Care and Life Sciences (HCLS) Interest Group has been a driving force behind a number of interesting Semantic Web-related ventures within the clinical and biological domains, including the [http://precedings.nature.com/documents/3686/version/1 Translational Medicine Ontology] and the [http://www.w3.org/TR/hcls-swan/ Semantic Web Applications in Neuroscience (SWAN) and [http://neurocommons.org/page/Main_Page Neurocommons] projects.

Each of these ventures rested on use of RDF or OWL to contribute in valuable ways to information exchange and integration in medical care and biological research. The initiatives formed a valuable supplement to the more general work of the W3C in supporting standards in the area of Semantic Technology, and the published results of these efforts shared the same standards of clarity and consistency as are characteristic of W3C-supported efforts in general. Their documentation has been carefully proofread by both domain experts and by those with expertise in logic and ontology, including people able to write coherent English.

Recently, however, HCLS has taken a strange turn, which is illustrated here:

http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability

Some samples, selected at random:

1. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/TermInfo
Structured clinical data is often viewed as being distributed between two "domains" (also called "views," "perspectives," "layers," "components," etc.) For the purposes of this discussion, we refer to those two "component parts of a fully-formed semantic utterance of clinical data" through by visualizing them as being distributed between two models: an Information Model and a Terminology Model. Note that the term "model" is used rather specifically in the context of this discussion for the purposes of building a concrete example, the terms Information Model and Terminology Model refer to specific, well-defined model, i.e. the HL7 RIM and the SNOMED-CT models. However the concepts of Information Model and Terminology Model in the larger discussion of the full representation of a fully-formed semantic utterance need not be restricted to a single Information Model or single Terminology Model. The critical feature about the separation of the two components is that each contains its own semantics, i.e. its own concepts, relationships, etc. In general, the Information Model expresses a network of generic concepts such roles, actions, observations and their inter-relationships, etc. -- this collection of information (small"i") is also often referred to as "meta-data" or "contextual knowledge." In contrast, the information (small "i") represented by the concepts, relationships, etc. in theTerminology Model provides specific "instance-level" descriptions of higher-order constructs. It is often heavily reliant on "is-a" and "a-part-of" relationships between concepts, and is sometimes referred to as the "data layer" or "definitional knowledge model." This is the conceptual view of the world, a view in which the Information and Terminology Models provide complementary semantics and therefore at least implicitly are clearly, cleanly, and consistently related to each other via some sort of "binding interface.

2. From http://www.w3.org/wiki/HCLS/ClinicalObservationsInteroperability/HL7_RIM
OWL distinguish two kinds of properties -- object and data type properties. Their domain is always a class. The range of an object property is a class, while the range of data type properties is a data type. For example, in RIM class figure above the classCode attribute within the Entity class has a type CS class. Additionally, the classCode attribute has a range constraint restricting it to contain only one value from the CS type (CS here represents a set of code described in the RIM vocabulary domain). There are two design options to represent the classCode attribute as an OWL object property. The first option can use the restriction feature of the OWL language:

Class: Entity
SubClassOf:
entity.classCode max 1 CS, entity.classCode min 1 CS

In this case restriction is applied on the Entity class. Please note that in addition to this restriction definition, first the classCode needs to described as an object property with a domain: Entity class and Range: CS class. For the second option, thanks to OWL 2 for allowing restrictions (i.e., minimum and maximum cardinality) on properties definition as below[.]

In sum, it seems that -- like so many other promising initiatives in medical IT -- HCLS has been taken over, at least in part, by the HL7 monster. I believe that the explanation for how this takeover could have occurred goes something like this. HL7 and HCLS are both volunteer efforts comprising people with good intentions who wish to advance the use and sophistication of information technology in clinical domains. When HL7 representatives volunteered to contribute to the work of HCLS they were, accordingly, greeted with open arms – not least given the fact that the HL7 community has been for some time itself talking of its standards as contributing to what they called 'semantic interoperability'.

For W3C talk of the ‘semantic interoperability’ of independent information systems signifies that these systems are able to exchange, correctly interpret, reuse and aggregate data. This is achieved by formalizing information to be exchanged using semantically well-defined languages such as RDF or OWL. "Semantics" here refers to traditional, model-theoretic semantics, as originally conceived by [http://www.hackettpublishing.com/philosophy/logic-semantics-metamathematics Alfred Tarski], and as utilized in ‘semantic technology’ for instance [https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-mt/index.html here]. (For background see [http://en.wikipedia.org/wiki/Semantics_(computer_science) here]. It is on this basis that the inferential and computational properties of OWL are defined -- just those properties which are widely held to lend significance to the work of W3C within the framework of HCLS and similar initiatives.

For HL7, in contrast, 'semantic interoperability' is something that is to be achieved by having multiple IT systems use (or be mapped) to a common reference information model called HL7 RIM. Several groups have attempted to create ontological representations of the RIM, but – for reasons discussed extensively on this [http://hl7-watch.blogspot.com/ blog] – such attempts have failed, because the RIM has no consistent documentation.

Consider, for example, the RIM’s treatment of its ‘Entity’ class, and some of its subclasses, which are defined as follows (from Health informatics: – HL7 version 3 – Reference information model – Release 4 (Document: ISO/HL7 21731:2011(E)):

Entity =def. A physical thing, group of physical things or an organization capable of participating in Acts while in a role.

:Living Subject =def. Anything that essentially has the property of life, independent of current state (a dead human corpse is still essentially a living subject).

:Health Chart Entity =def. A health chart included to serve as a document receiving entity in the management of medical records.

:Material = def. Any thing that has extension in space and mass, may be of living or non-living origin.

::ManufacturedMaterial =def. An Entity or combination of Entities transformed for a particular purpose by a manufacturing process.

:::Device =def. A subtype of ManufacturedMaterial used in an activity, without being substantially changed through that activity.

::::Certificate Representation =def. A physical artifact that stores information about the granting of authorization.

::::Imaging Modality =def. Class to contain unique attributes of diagnostic imaging equipment.

One could talk at great length about the problems with this hierarchy, but just to mention the most obvious problems, how, given the definition of ‘Material Entity’ can ‘unique attributes of diagnostic imaging equipment’ be material entities. What do ‘unique’ and ‘attribute’ mean in the definition of ‘Imagine Modality’ here? And in what sense is “a dead human corpse … still essentially a living subject”?