Page tree
Skip to end of metadata
Go to start of metadata

Topics

  • mCODE Overall Model
  • Profile Tour by Category
    • Patient
    • Disease
    • Treatment
    • Lab/Vital
    • Outcome

Profile Summary by mCODE Category

  

General Notes

  • For all resources, the following should always be present:
    • Reference to patient/subject
    • Relevant time associated to the information
    • Workflow status of observations
    • References to encounters
    • Fixed codes for observations
  • By the numbers:
    • 91 (non-metadata) must support elements
    • 23 profiles
    • 6 extensions
    • 25 value sets

Helpful Definitions 

  • Must support – implementation shall provide “meaningful support” for the element.
    • In mCODE, must support is interpreted as the mCODE data sender must send the data (if it is known) and the mCODE data receiver shall be capable of receiving and storing the data.
  • Required elements – a data sender must provide each required element or an explicit “data absent reason” for each missing data item.
    • A required element has a cardinality of 1..1. However, if the element is contained by an optional element, then it is not required unless its containing element is present in a given instance of the profile.

Abstract Profiles

  • Abstract profiles are profiles on resources or data types that describe patterns used by other profiles, but can't be instantiated directly.
    • I.e. instances can conform to profiles *based* on these abstract profiles, but don't declare conformance to the abstract profiles themselves.
    • Creating abstract profiles promotes inheritance for profiles that share common attributes.

  • PrimaryCancerCondition and SecondaryCancerCondition are derived from the abstract profile CancerConditionParent.

    • The TNM Staging profiles are derived from the abstract profile CancerStageParent.

Data Dictionary 

  • The purpose of the data dictionary is to provide a summary of the mCODE data elements. It does NOT provide the full details needed to exchange mCODE elements.
  • External profiles and value sets are not included.
  • Document organization
    • Profile Sheet = list of profiles within which mCODE data elements are expected to be exchanged
    • Data Elements Sheet = details for the must support data elements contained within each profile.
    • Value Set Sheet = list of mCODE-defined value sets
    • Value Set Details Sheet = contains individual codes associated with each mCODE-defined value set


  • No labels