Sample Table
- Field
- Field
- Field (as many fields listed as are applicable)
- Note (if applicable)
Obs
concept_id (id of question concept)
value_coded (id of coded answer)
Obs for L are retired (with note), and then new obs are generated with W concept_id.
Drug
concept_id
route
dosage_form
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.
Drug_ingredient
**functionality not yet available**
- concept_id (id of an ingredient concept)
- unit
Orders
concept_id
Field
concept_id (for all entries with a field_type=1 (concept))
Program
concept_id
Program_workflow
concept_id
Program_workflow_state
concept_id
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