ART Terminology Association Viewer - Revision history

Ahenket: /* Form parameters */

2017-10-04T11:02:13Z

‎Form parameters

Ahenket: /* Form parameters */

2017-10-04T10:58:48Z

‎Form parameters

Admin at 15:53, 21 May 2016

2016-05-21T15:53:06Z

Mligtvoet: /* Form parameters */

2015-08-27T07:50:30Z

‎Form parameters

Ahenket: /* Terminology Association Viewer */

2015-08-26T14:50:56Z

‎Terminology Association Viewer

Kheitmann at 09:10, 7 August 2014

2014-08-07T09:10:10Z

Mligtvoet: /* Terminology Association Viewer */ fixed typo

2014-07-21T05:38:46Z

‎Terminology Association Viewer: fixed typo

Ahenket: Created page with "===Terminology Association Viewer=== A terminology association defines the binding of dataset concepts to relevant terminology. Associations may be done at three levels: * An ..."

2014-03-02T12:27:12Z

Created page with "===Terminology Association Viewer=== A terminology association defines the binding of dataset concepts to relevant terminology. Associations may be done at three levels: * An ..."

New page

===Terminology Association Viewer===
A terminology association defines the binding of dataset concepts to relevant terminology. Associations may be done at three levels:
* An association with the concept itself, e.g. to use in HL7 V3 observation/code. This is normally a single code.
* An association with a list of codeable concepts, e.g. to use in HL7 V3 observation/value. This is normally a value set
* An association for individual concepts in a dataset concept list to bind the exact value set member. This is normally a single code

With the terminology association viewer ART provides a targeted overview of the bindings that were applied. Note that this very same info is integrated into the read only display of dataset concepts anywhere they appear. The terminology association viewer turns into the [[ART Terminology Association Editor]] when are logged in as an editor of the project.

The screenshot shows associations at 2 levels. There's value set binding to AdministrativeGender (you can go right to the value set by clicking its name), and there are two individual bindings to value set members. Since the concept is itself has a direct representation in HL7 V3 as the administrativeGenderCode, there is no use case for a concept level binding.

[[Image:TerminologyAssociationViewer.png|center|700px]]

@@ Line 41: / Line 41: @@
 | language
 | Displays contents in the requested language. When contents are not available in the requested language, there will be nothing to display. Example en-US, or nl-NL.
-| ''1.8.51''
+| art v1.8.51
 |}

@@ Line 15: / Line 15: @@
 <syntaxhighlight lang="text" enclose="div">
-/decor-terminology--[prefix]?datasetId=[dataset id]&datasetEffectiveDate=[dataset effective date]&conceptId=[concept id]&conceptEffectiveDate=[concept effective date]
+/decor-terminology--[prefix]?datasetId=[dataset id]&datasetEffectiveDate=[dataset effective date]&conceptId=[concept id]&conceptEffectiveDate=[concept effective date]&language=[ll-CC]
 </syntaxhighlight>
@@ Line 38: / Line 38: @@
 | Selects the dataset concept with this effective date in the selected transaction. Format: yyyy-mm-ddThh:mm:ss. Works only in combination with param conceptId
 | art v1.5
 |}

@@ Line 18: / Line 18: @@
 </syntaxhighlight>
-{| style="text-align: left;" class="artdecor"
+{| style="text-align: left;" class="artdecorwiki"
 ! Parameter !! Description !! Since
 |-

@@ Line 14: / Line 14: @@
 The terminology association form, as most other forms, supports parametrization.
-<syntaxhighlight lang="text">
+<syntaxhighlight lang="text" enclose="div">
 /decor-terminology--[prefix]?datasetId=[dataset id]&datasetEffectiveDate=[dataset effective date]&conceptId=[concept id]&conceptEffectiveDate=[concept effective date]
 </syntaxhighlight>

← Older revision		Revision as of 14:50, 26 August 2015
Line 10:		Line 10:

	[[Image:TerminologyAssociationViewer.png\|center\|700px]]		[[Image:TerminologyAssociationViewer.png\|center\|700px]]
		+
		+	=Form parameters=
		+	The terminology association form, as most other forms, supports parametrization.
		+
		+	<syntaxhighlight lang="text">
		+	/decor-terminology--[prefix]?datasetId=[dataset id]&datasetEffectiveDate=[dataset effective date]&conceptId=[concept id]&conceptEffectiveDate=[concept effective date]
		+	</syntaxhighlight>
		+
		+	{\| style="text-align: left;" class="artdecor"
		+	! Parameter !! Description !! Since
		+	\|-
		+	\| prefix \|\| Project prefix \|\| ''always''
		+	\|-
		+	\| datasetId
		+	\| Selects the project dataset with this id. Format: OID
		+	\| ''always''
		+	\|-
		+	\| datasetEffectiveDate
		+	\| Selects the project dataset with this effectiveDate. Format: yyyy-mm-ddThh:mm:ss.
		+	\| art v1.5
		+	\|-
		+	\| conceptId
		+	\| Selects the dataset concept with this id in the selected transaction. Format: OID. Param only works if the param id points to a transaction that binds the dataset that contains this concept.
		+	\| ''always''
		+	\|-
		+	\| conceptEffectiveDate
		+	\| Selects the dataset concept with this effective date in the selected transaction. Format: yyyy-mm-ddThh:mm:ss. Works only in combination with param conceptId
		+	\| art v1.5
		+	\|}

@@ Line 1: / Line 1: @@
-===Terminology Association Viewer===
+=Terminology Association Viewer=
 A terminology association defines the binding of dataset concepts to relevant terminology. Associations may be done at three levels:
 * An association with the concept itself, e.g. to use in HL7 V3 observation/code. This is normally a single code.

@@ Line 5: / Line 5: @@
 * An association for individual concepts in a dataset concept list to bind the exact value set member. This is normally a single code
-With the terminology association viewer ART provides a targeted overview of the bindings that were applied. Note that this very same info is integrated into the read only display of dataset concepts anywhere they appear. The terminology association viewer turns into the [[ART Terminology Association Editor]] when are logged in as an editor of the project.
+With the terminology association viewer ART provides a targeted overview of the bindings that were applied. Note that this very same info is integrated into the read only display of dataset concepts anywhere they appear. The terminology association viewer turns into the [[ART Terminology Association Editor]] when you are logged in as an editor of the project.
 The screenshot shows associations at 2 levels. There's value set binding to AdministrativeGender (you can go right to the value set by clicking its name), and there are two individual bindings to value set members. Since the concept is itself has a direct representation in HL7 V3 as the administrativeGenderCode, there is no use case for a concept level binding.
 [[Image:TerminologyAssociationViewer.png|center|700px]]