1 / 14

Data Migration vs Data Transfer

Data Migration vs Data Transfer. Leo Fogarty Dunblane 5/11/08. Semantic Elements. Which sit in a context which might include:. Relating to an ongoing Problem: Chest Pain. Which was constructed during an event: Surgery Consultation. Which all sits in a document: “Referral Letter”.

fostrander
Télécharger la présentation

Data Migration vs Data Transfer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Data MigrationvsData Transfer Leo Fogarty Dunblane 5/11/08

  2. Semantic Elements Which sit in a context which might include: Relating to an ongoing Problem: Chest Pain Which was constructed during an event: Surgery Consultation Which all sits in a document: “Referral Letter” A Heading: “Past History” Modifying Information: Q= “Possible” or The Record of Patient Information as Text:- which is human-readable and easily communicable The inclusion of codes: XE2uV Ischaemic Heart Disease Which may be qualified as: X793b Mild X78th First Episode

  3. Elements of Data Transfer • Methodology • Model • Technical Specification • Implementation Guide • Application Functionality Rules • Iterative Development • Testing • Roll-Out

  4. GP2GP Model

  5. Message Viewing

  6. An Allergy -<CompoundStatement classCode="CATEGORY"> <idroot="3D4352FC-9C61-46A9-81C5-D5736F36D07B" /> <codecode="14L..00" codeSystem="2.16.840.1.113883.2.1.6.2" displayName="H/O: drug allergy" /> <statusCodecode="COMPLETE" /> <effectiveTimenullFlavor="NI" /> <availabilityTimevalue="20060301" /> -<component> -<ObservationStatement> <idroot="8826D45B-3530-4FBB-9FB2-ABDFAEABDDB3" /> <codecode="14L..00" codeSystem="2.16.840.1.113883.2.1.6.2" displayName="H/O: drug allergy" /> <statusCodecode="COMPLETE" /> <effectiveTimenullFlavor="NI" /> <availabilityTimevalue="20060301" /> -<value xsi:type="CD" code="ALLERGY-EMISDRUGGROUP-3.1" codeSystem="2.16.840.113883.2.1.6.3" displayName="Adverse reaction to Bronchodilators"> <originalText>Adverse reaction to Bronchodilators</originalText> </value> </ObservationStatement> </component> </CompoundStatement>

  7. Non-Interoperable Items • Allergies • Some Prescribable Products • Attachments Incomplete • Non-code codes • Immunisations • Local Codes • Local Idiosyncratic Data Structures

  8. Elements of Data Migration • Individual Record Contents much the same but….. • Migration – many records not one • Other aspects of systems • Appointments • Agents Directory • Reports etc

  9. Elements of Data Migration • No existing standard • Many one-to-one solutions • Variable results • GPSoC Validation in England

  10. Non-migratable Items • Everything from the data transfer list plus: • Difficulties migrating between coding schemes • Appointments • Reports • Document management

More Related