ErgoSoftUK at 15:57, 1 July 2020

2020-07-01T15:57:09Z

← Older revision		Revision as of 15:57, 1 July 2020
Line 94:		Line 94:

	==== Node details ====		==== Node details ====
	The mapping node is the effecive starting point for the maps. It represents a ~~specific~~ set of codes or values within a specific context scenario. The node has associated with it its own identifier for convenience and a concept representing the data model property of that node.<syntaxhighlight lang="mysql">		The mapping node is the effecive starting point for the maps. It represents a set of codes or values within a specific context scenario. The node has associated with it its own identifier for convenience and a concept representing the data model property of that node.<syntaxhighlight lang="mysql">
	CREATE TABLE map_node (		CREATE TABLE map_node (
	id INT AUTO_INCREMENT,		id INT AUTO_INCREMENT,
Line 114:		Line 114:

	==== Node mappings ====		==== Node mappings ====
	For each node, a number of mappings exist, from either a code or a term, to an Information Model concept.<syntaxhighlight lang="mysql">		For each node, a number of mappings exist, from either a code or a term within that node context, to an Information Model concept.<syntaxhighlight lang="mysql">
	CREATE TABLE map_node_value (		CREATE TABLE map_node_value (
	id INT AUTO_INCREMENT,		id INT AUTO_INCREMENT,
Line 149:		Line 149:

	=== Functional implementation ===		=== Functional implementation ===
	<br />		A single general mapping api will be exposed which can be called with any of the standard Map????Request structures. The existing IM client wrapper library will be extended to include mapping api calls for simplified internal use.

			==== Node identification ====
			Fore property concept lookups, a distinct node search is performed on the map_context table, matching on all available columns. If multiple matches are found (for example where provider is not supplied but 2 provider rows exist and point to different nodes) then an exception is thrown.

			If no match is found then a new (draft) map_context row is inserted along with corresponding map_node and concept entries, using all available data.

			Once the node is identified (or created), the associated property concept can be retrieved.

			==== Node mappings ====
			For value mappings, an additional search is performed on the map_node_value table, based on the node id and the code/term. Again if no match is found, a new (draft) concept is created and added to the mapping list.<br />

ErgoSoftUK at 13:49, 1 July 2020

2020-07-01T13:49:13Z

← Older revision		Revision as of 13:49, 1 July 2020
Line 58:		Line 58:
	!Table		!Table
	!Column		!Column
			!Node
	\|-		\|-
	\|/BRTS/CRNR/CDS/EMGCY/department_type		\|/BRTS/CRNR/CDS/EMGCY/department_type
Line 65:		Line 66:
	\|		\|
	\|		\|
			\|/CDS/EMGCY/department_type
	\|-		\|-
	\|		\|
Line 72:		Line 74:
	\|emergency		\|emergency
	\|department_type		\|department_type
			\|/CDS/EMGCY/department_type
	\|-		\|-
	\|/BRTS/CRNR		\|/BRTS/CRNR
Line 79:		Line 82:
	\|emergency		\|emergency
	\|department_type		\|department_type
			\|/CDS/EMGCY/department_type
	\|-		\|-
	\|/HMRTN/CRNR/EMGNCY/department_type		\|/HMRTN/CRNR/EMGNCY/department_type
Line 86:		Line 90:
	\|		\|
	\|		\|
			\|/CDS/EMGCY/department_type
	\|}		\|}

ErgoSoftUK: Initial draft

2020-07-01T13:26:25Z

Initial draft

Show changes

ErgoSoftUK: Created blank page

2020-07-01T12:42:28Z

Created blank page

New page

Data map API Spec - Revision history

ErgoSoftUK at 15:57, 1 July 2020

ErgoSoftUK at 13:49, 1 July 2020

ErgoSoftUK: Initial draft

ErgoSoftUK: Created blank page