Child pages
  • Testing Merge Concept Module
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

Sample Table

  • Field 
  • Field 
  • Field (as many fields listed as are applicable)
  • Note (if applicable) 

Obs

  • concept_id (id of question concept, numeric question)
  • concept_id (id of question concept, coded question)
    • currently has logic issues regarding coded answers (8/16/13)
  • concept_id (id of question concept, freetext question)
  • value_coded (id of coded answer)
  • Obs for Loser concept_id are retired (with note), and then new obs are generated with Winner concept_id. 

Drug

  • concept_id
    • while the Merge Concept preview page displays the references to the to-be-merged concepts in the drug table, the table is not impacted after the merge is complete (8/16/13)
  • route
    • the Merge Concept preview page does not display the reference to the to-be-merged concept in the drug table, and the table is not impacted after the merge is complete (8/16/13)
  • dosage_form
    • the Merge Concept preview page does not display the reference to the to-be-merged concept in the drug table, and the table is not impacted after the merge is complete (8/16/13)
  • Output to notify user of places where the drug table was impacted, so that the user can then double check to ensure subsequent drug formularies don’t exist and, if they do, resolve them manually. Perhaps future iterations of MCM can take the next step of resolving any existing or created (through the merge) duplicate drug formularies. **functionality not yet available** 

Drug_ingredient

**functionality not yet available** 

  • concept_id (id of an ingredient concept)
  • unit

Orders

  • concept_id
  • Orders with Loser concept_id are updated to now have the Winner concept_id

Field

  • concept_id (for all entries with a field_type=1 (concept))
  • name
  • description
    • the Merge Concept preview page correctly displays the form with references to the to-be-merged concepts in the Field table, and the concept_id column is properly updated with the Winner concept. However, even though the Loser concept_id was updated, it seems that the "name" and "description" columns from the Loser concept also need to be updated with the Winner concept's information. Otherwise, those fields will still contain metadata from the Loser concept in the Field table. (8/16/13)

Program

  • concept_id
  • name
  • description
    • the Merge Concept preview page correctly displays the form with references to the to-be-merged concepts in the Program table, and the concept_id column is properly updated with the Winner concept. However, even though the Loser concept_id was updated, it seems that the "name" and "description" columns from the Loser concept also need to be updated with the Winner concept's information. Otherwise, those fields will still contain metadata from the Loser concept in the Field table. (8/16/13)

Program_workflow

  •  concept_id
    • the Merge Concept preview page does not currently display concept references in the Program_workflow table

Program_workflow_state

  •  concept_id
    • the Merge Concept preview page does not currently display concept references in the Program_workflow_state table

Person_attribute_type

  • foreign_key (if format = concept)

Concept

  • concept_id

Concept_answer

  • concept_id (id of question concept)

  • answer_concept (id of the answer concept)

  • duplicate concept_answer (uniquely identified via concept_answer_id) will be deleted, kept track of in a log, so long as all of the old data is also updated so that later updating an old encounter wouldn't fail validation **functionality not yet available** 

Concept_name

  • concept_id

  • Synonyms for L are not added to W concept, if not already present.

Concept_set

  • concept_id (id of set member)

  • concept_set (id of concept set parent)

Concept_numeric

  • concept_id **functionality not yet available** 

Concept_complex

  • concept_id **functionality not yet available**  

Logs/Output for the user

**functionality not yet available**

  • Potential duplicates created, as a result of the merge: Drugs, Programs, Orders, Concept Sets, Person Attribute Types
  • Text references: HTML Forms, Global Properties, etc.
  • Event published that other modules can subscribe to (if they use concepts in their tables) and handle accordingly

Other

  • Optimizing merges to handle a very large load of data 


  • No labels