...
In order to be able to create re-usable application modules, e.g. Task Plans, GDL guidelines, UI forms etc, these latter cannot directly contain the meta-data needed to enable the data retrieval to work for particular back-end systems.
A Specification Model
Rough ideas on specifying a binding using the above model.
| Code Block |
|---|
DATA_SET antenatal_1.v1.0.3
items
SINGLE
name = "date_of_birth"
type = "Date"
frame_id = "basic_admin"
path = "xxxx"
value = Result
SINGLE
name = "systolic_bp"
type = "Quantity"
frame_id = "bp_obs"
path = "/data[id2]/events[id7]/data[id4]/items[id5]"
currency = "PT15s"
value = Result
SINGLE
name = "diastolic_bp"
type = "Quantity"
frame_id = "bp_obs"
path = "/data[id2]/events[id7]/data[id4]/items[id5]"
currency = "PT15s"
value = Result
SINGLE
name = "is_type1_diabetic"
type = "Boolean"
frame_id = "is_diabetic"
path = "/data[id2]/items[id3]"
value = ???
binding["env_A"]
DATA_RETRIEVE_FRAME
frame_id = "basic_admin"
method
QUERY_CALL
system_id = pas3.nhs.org.uk
call_name = fhir_admin_request
parameters
"xxxx = abc"
"yyyy" = "def"
DATA_RETRIEVE_FRAME
frame_id = "bp_obs"
method
QUERY_CALL
system_id = ehr1.nhs.org.uk
call_name = aql_execute
query_text = "xxxx"
DATA_RETRIEVE_FRAME
frame_id = "is_type1_diabetic"
method
QUERY_CALL
system_id = ehr1.nhs.org.uk
call_name = aql_execute
query_text = "xxxx"
|