Size: px
Start display at page:

Download ""

Transcription

1

2 Semantic Interoperability I got your message I can understand it I know what you mean I believe you I know what I will do

3 I got your message

4 I understand it Syntax Content Rich Information Models Clear message specifications Understood by both parties Clinical statements Free text Images Sound

5 I know what you mean For computers, this is not easy Shared syntax Shared information models Shared language either interface terminology such as READ / LOINC or reference terminology such as SNOMED CT Maps / translations / transformations / functions into a classification terminology such as ICD10 Create new content, such as alert clinical statements

6 What does the LRA do It enables data and the uses of data to be described It enables the data required to inform patient care to be obtained as a by-product of the records used for patient care. It enables the data required to inform the design and management of healthcare systems to be obtained as a by-product of the records used for patient care.

7 What is the LRA It is Logical Architecture For Health and Social care records Driven by English National Health and Social Care requirements Based on EN13606 Exploiting the potential of SNOMED CT terminology It isn t The answer to life the universe and everything A physical model Designed to be implemented as a physical system Fully elaborated yet

8 The English Journey General Practitioner (family doctor) systems using MIQUEST for over 10 years Very simple model Pre-coordinated mono-axial terminology Patients Journals Encounters Journals Referrals Links

9 The future Mixed economy GP Data in READ with Miquest based queries GP Data using forms and templates Acute data from Millennium and Lorenzo using question/answer forms Acute data from note taking functionalities

10 Success and challenges Physician office READ interface terminology Journal of simple clinical statements Physicians generate content from terminology Hospitals Question and answer forms Creating enough forms is, at best, challenging Systems need the forms for deployment

11 Content is King A standard structure is important, but You need content to make it worthwhile

12 Note Taking

13 Note Taking

14 31 Octember 921 S: Sore throat 4 days temperature, taking fluids taking paracetamol. No better. O: Looks well, enlarged glands, pus - tonsils A: Folicular tonsilitis P: Penicillin V 250mg 2qds 40

15 31 Octember 921 S: Sore throat 4 days temperature, taking fluids taking paracetamol. No better. O: Looks well, enlarged glands, pus - tonsils A: Folicular tonsilitis P: Penicillin V 250mg 2qds 40 Composition

16 31 Octember 921 S: Sore throat 4 days temperature, taking fluids taking paracetamol. No better. O: Looks well, enlarged glands, pus - tonsils A: Folicular tonsilitis P: Penicillin V 250mg 2qds 40 Composition Entry

17 31 Octember 921 S: Sore throat 4 days temperature, taking fluids taking paracetamol. No better. O: Looks well, enlarged glands, pus - tonsils, Temp 38.1 A: Folicular tonsilitis P: Penicillin V 250mg 2qds 40 Composition Entry Element

18 Sore throat 4 days Meaning: The patient reported that the patient had a sore throat at the specified time Entry time: 31 Octember 921 Observation time: 28 Octember 921 to 31 Octember 921

19 Pus -Tonsils Meaning: The patient had pus - tonsils known to be present at the time Entry time: 31 Octember 921 Observation time: 31 Octember 921

20 Temp 38.1 Meaning: The patient had a temperature (observable) known to be present at the time Entry time: 31 Octember 921 Observation time: 31 Octember 921 Value: 38.1 Unit: degrees celsius

21 PDS SDS DM+D HL7 style actors and participations EN13606 SNOMED CT ISO datatypes (HL7 datatypes V2) UCUM Meaning: The patient had a temperature (observable) known to be present at the time Entry time: 31 Octember 921 Observation time: 31 Octember 921 Value: pq.value 38.1 pq.unit degrees celsius

22 The base elements Element Observation Activity Relationship Property Finding Investigation Substance Activity General Activity

23

24 An example constraint situation with explicit context : { associated procedure = << measuring height of patient, procedure context = < context values for actions, temporal context = < temporal context value, subject relationship context = < person }

25 An example Blood pressure

26 An example Blood pressure

27 Haemodialysis Vascular Access

28

29 LRA Factory Machine (the next year s development) Requirements: Laws, guidelines, Frameworks, standards etc Archetypes/templates

30 More information