Contents 1 Introduction 2 Participation 3 Activity 3.1 Current Model 3.2 Concept_Name: Extended Concept Model 3.2.1 Notes 3.3 Concept_Name: Concept Proposal Modifications 3.3.1 Notes 3.4 Proposal: Concept-Reference Table Mapping Enhancement 3.5 Proposal: Extended Form Fields 3.6 Miscellaneous Changes

Introduction

The Data Model working group is interested in the design and implementation of a flexible representation of clinical patient information which supports aggregated reporting.

Participation

Activity

Current Model

• Data Model: image of current schema
• Data Model Documentation: detailed notes about the schema

Concept_Name: Extended Concept Model

The data model needs to be extended to accommodate internationalization and specialization of concepts.

Notes

• Extended Concept Model Requirements
• MVP Concept Data Model Changes
• MVP Patient Consent Data Model Changes
• Image:Alternate.png -- Paul's diagram of a how to accommodate the changes

Concept_Name: Concept Proposal Modifications

The concept_proposal table needs to accommodate the internationalization changes by including locale and at least one tag.

I think that we need to support at least the tags we recognize now as being need for the terminology service bureau. That would be Preferred Language and Preferred Location flags. --Akanter 17:15, 21 May 2007 (EDT)

Notes

• Image:concept_proposal_changes.png - isolated diagram showing the changes to concept_proposal

Proposal: Concept-Reference Table Mapping Enhancement

Link to Forum discussion and documentation

Proposal: Extended Form Fields

In order to provide more for different uses of forms (InfoPath, Xforms, Touch Screen etc) it has been suggested that an 'field attribute' table should be added.

(this section can be used to gather requirements and to draw up a more formal proposal)

Miscellaneous Changes

• *.voided - could be deprecated. The state of voided_by is sufficient to determine whether the related record has been voided.
• *.creator - could be renamed to created_by to be consistent with other user names, like voided_by and changed_by.
• concept_proposal table - could be deprecated. The table must be kept up to date with changes to the full set of concept tables (concept _class, concept, concept_name, concept_name_tag). Rather than mirror all the needed fields, the proposed concepts could be kept in the normal concept tables, but also have an entry in the concept_proposal table to track the workflow from proposal to approval.