Case testNormalUseRestMetadata003

Overview

Test case for normal use of the REST routine retrieving all metadata for a terminology and version

Procedure 1:  SNOMEDCT/RF2 loader test

• Authenticate "viewer.user" with "viewer.password"
• Retrieve SNOMEDCT/latest metadata

• Test Each Type of Metadata

  • Attribute Descriptions

    • TEST: Expect 99
    • TEST: Expect 

      SCTID: 900000000000461009

      Concept type component (foundation metadata concept)
      Concept type component

  • Attribute Types

    • TEST: Expect 19
      • NOTE:  In current SNOMEDCT data (as of 3/1/15),  707000009, SNOMED CT parsable string (foundation metadata concept) exists, not in test data
    • TEST: Expect 

      SCTID: 447638001

      Map source concept cannot be classified with available data (foundation metadata concept)
      Map source concept cannot be classified with available data

  • Attribute Value Refsets

    • TEST: Expect 5
    • TEST: Expect

      SCTID: 900000000000489007

      Concept inactivation indicator attribute value reference set (foundation metadata concept)
      Concept inactivation indicator attribute value reference set
      Concept inactivation indicator reference set

  • Case Significances

    • TEST: Expect 3
    • TEST: Expect

      SCTID: 900000000000020002

      Only initial character case insensitive (core metadata concept)
      Initial character case insensitive
      Only initial character case insensitive

  • Characteristic Types

    • TEST: Expect 5
    • TEST: Expect 

      CTID: 900000000000011006

      Inferred relationship (core metadata concept)
      Inferred relationship

  • Complex Map Refsets

    • TEST: Expect 3
    • TEST: Expect 

      SCTID: 447563008

      ICD-9-CM equivalence complex map reference set (foundation metadata concept)
      ICD-9-CM equivalence complex map reference set

  • Definition Statuses

    • TEST: Expect 2
    • TEST: Expect 

      SCTID: 900000000000073002

      Sufficiently defined concept definition status (core metadata concept)
      Defined
      Necessary and sufficient definition
      Sufficiently defined concept definition status

  • Description Formats
    • TEST: Expect 4
    • TEST: Expect

      SCTID: 900000000000541001

      Limited HyperText Markup Language (foundation metadata concept)
      Limited HTML
      Limited HyperText Markup Language

  • Description Types
    • TEST: Expect 3
    • TEST: Expect 

      900000000000550004

      Definition (core metadata concept)
      Definition

  • Hierarchical Relationship Types
    • TEST: Expect 1
    • TEST: Expect

      SCTID: 116680003

      Is a (attribute)
      Is a

    • TEST: All hierarchical relationship types must be relationship types
  • Inferred Characteristic Type
    • TEST: Expect 1
    • TEST: Expect

      900000000000011006

      Inferred relationship (core metadata concept)
      Inferred relationship

    • TEST: All inferred characteristic types must be characteristic types

  • Language Refsets

    • TEST: Expect 4
    • TEST: Expect 

      SCTID: 900000000000507009

      English [International Organization for Standardization 639-1 code en] language reference set (foundation metadata concept)
      English
      English [International Organization for Standardization 639-1 code en] language reference set

  • Map Relations (Reference Set Attribute)

    • TEST: Expect 14 (6 from Reference Set Attribute
      • 8 from 447634004:  ICD-10 map category value (foundation metadata concept)
      • 6 from 447247004: SNOMED CT source code to target map code correlation value (foundation metadata concept)
    • TEST: Expect 

      SCTID: 447559001

      Broad to narrow map from SNOMED CT source code to target code (foundation metadata concept)
      Broad to narrow map from SNOMED CT source code to target code

  • Modules
    • TEST: Expect 6
    • TEST: Expect

      SCTID: 900000000000012004

      SNOMED CT model component module (core metadata concept)
      SNOMED CT model component
      SNOMED CT model component module

  • Module Dependency Refsets

    • TEST: Expect 1

    • TEST: Expect

      SCTID: 900000000000534007

      Module dependency reference set (foundation metadata concept)
      Module dependency
      Module dependency reference set

  • Non-grouping Relationship Types

    • TEST: Expect 4
      • These are hardcoded in SnomedMetadataServiceJpaHelper.getNonGroupingRelationshipTypes()
      • Concepts are:  "123005000", "272741003", "127489000", "411116001"
    • TEST: Expect

      SCTID: 272741003

       

      Laterality (attribute)
      Laterality

    • TEST: All non-grouping relationship types must be relationship types
  • Refset Descriptor Refsets
    • TEST: Expect 1
    • TEST: Expect 

      SCTID: 900000000000456007

      Reference set descriptor reference set (foundation metadata concept)
      Reference set descriptor
      Reference set descriptor reference set

  • Relationship Modifiers

    • TEST: Expect 2
    • TEST: Expect

      SCTID: 900000000000451002

      Existential restriction modifier (core metadata concept)
      Existential restriction modifier
      Some

  • Relationship Types

    • TEST: Expect 63 (62 + "Is a" relationship)
    • TEST: Expect

      SCTID: 260507000

      Access (attribute)
      Access

  • Simple Map Refsets

    • TEST: Expect 3
      • NOTE: Current SNOMEDCT (as of 3/1/2015) also includes 467614008, GMDN simple map reference set (foundation metadata concept)
    • TEST: Expect 

      SCTID: 446608001

      ICD-O simple map reference set (foundation metadata concept)
      ICD-O simple map reference set

  • Simple Refsets

    • TEST: Expect 23
    • TEST: Expect 

      SCTID: 447565001

      Virtual therapeutic moiety simple reference set (foundation metadata concept)
      Virtual therapeutic moiety simple reference set

  • Stated Characteristic Types
    • TEST: Expect 1
    • TEST: Expect

      SCTID: 900000000000010007

      Stated relationship (core metadata concept)
      Stated relationship

    • TEST: All stated characteristic types must be characteristic types

Procedure 2:  ICD9CM/ClaML loader test

The ClamL loader test is simpler, as the full data is loaded instead of a truncated portion.  Concept names are not checked.

• Retrieve ICD9CM/2013 metadata
• Authenticate "viewer.user" with "viewer.password"
• Retrieve SNOMEDCT/latest metadata

• Test Each Type of Metadata

  • Case Significances:
    • TEST: Expect 1
  • Characteristic Types:
    • TEST: Expect 1
  • Definition Statuses
    • TEST: Expect 1
  • Description Types
    • TEST: Expect 13
  • Hierarchical Relationship Types
    • TEST: Expect 1
    • TEST: All hierarchical relationship types must be relationship types
  • Inferred Characteristic Types
    • TEST: Expect 1
    • TEST: All inferred characteristic types must be characteristic types
  • Modules:
    • TEST: Expect 1
  • Relationship Modifiers
    • TEST: Expect 1
  • Relationship Types
    • TEST: Expect 4
  • Simple Refset Types
    • TEST: Expect 2
  • Stated Characteristic Types
    • TEST: Expect 1
    • TEST: All stated characteristic types must be characteristic types
  • All other metadata keys in MetadataKeys
    • TEST: Expect 0

Expected Runtime

• < 10s

Notes

• If sample data for either SNOMEDCT or ICD9CM is updated, this test will need to be revised with the correct expected numbers and concepts.