SNOMED Documentation Search


 Other Documents

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Factors that need to be considered include:

  • Anchor
    _38eb3128-9254-425c-b301-b8e3a4e4885e__9
    _38eb3128-9254-425c-b301-b8e3a4e4885e__9
    The volume and value of existing content, in the context of the anticipated uses of a future
    Glossary ref
    SNOMED CT application
    :
    • The scale of the task and the potential value of migrated data are interrelated. Relatively small amounts of data that are of debatable value to a future system may not justify an elaborate migration process. On the other hand, it is vital to ensure that valuable existing data remains fully accessible within a
      Glossary ref
      SNOMED CT enabled application
      .

Example: In the UK alone, there are over 50 million patients primary care electronic records coded using one of the versions of the

Glossary ref
Read Codes
. Based on typical patterns of use this means there are several billion coded record entries that may need to be taken into account in the migration process. A substantial proportion of this data has continuing clinical value and thus despite the scale of the task it is important to ensure that data is migrated accurately and efficiently.

  • Data quality and consistency:
    Anchor
    _38eb3128-9254-425c-b301-b8e3a4e4885e__3
    _38eb3128-9254-425c-b301-b8e3a4e4885e__3
    • Different users in different settings may select codes and terms in idiosyncratic ways to reflect their needs. This may be acceptable locally but it creates an obstacle to migration if the goal is consistent and comparable information at a regional, national or global level.
  • Different source code systems:
    Anchor
    _38eb3128-9254-425c-b301-b8e3a4e4885e__6
    _38eb3128-9254-425c-b301-b8e3a4e4885e__6
    • Several different coding scheme versions are in use and each of these poses specific challenges and offers a different profile of potential benefits.
  • Different information systems:
    Anchor
    _38eb3128-9254-425c-b301-b8e3a4e4885e__e
    _38eb3128-9254-425c-b301-b8e3a4e4885e__e
    • There are many system suppliers. As a result of system development and commercial mergers and takeovers, many suppliers support more than one application in the same domain. The challenge is to migrate from this diverse situation to a next generation environment supporting standards such as
      Glossary ref
      SNOMED CT
      .
  • Different information models:
    Anchor
    _38eb3128-9254-425c-b301-b8e3a4e4885e__2
    _38eb3128-9254-425c-b301-b8e3a4e4885e__2
    • In addition to differences in the use of codes, existing systems inevitably have a variety of approaches to structuring clinical information. As a result, the process of migrating data between systems is not simply a question of converting codes. The underlying architecture of the source data also needs to be taken into account to make optimal use of existing data without losing processable information or introducing errors.