Lexevs Gap Analysis Meeting Minutes

LexEVS Gap Analysis Meeting Minutes

Meeting Name: / Concept Domains and Usage Context / Location:
Date: / Time:
Facilitator: / Craig / Attendees:
Conf. Line
Topic / Discussion Points / Action Items
·  Concept Domain and Usage Context Gap Analysis / Concept Domain - is essentially a coding system. Put a wrapper class around ?
HL7 compliance requirements - need to consider looking at specific model (consider 11179).
Look at Value Sets that are bound to the Concept Domain. (not sure if HL7 specific or not)
ruleSet
Spec does not address how to create standard rule set which makes value sets non-standard and non-portable. We will propose the same set of concrete rules that HL7 uses (current LexEVS) with addition of property.
We will examine a fifth type of value def entry. One that has rule set uri+version identifier? Will discuss what the API to that may look like.
ValueDomainDefinity - add ConceptualDomain (will be reference to supportedConceptualDomain) this gives the local Identifier and URI (point to coding scheme).
6.2.3.2
Should we consider a concept domain type (entity). Do we gain anything from it?
How many concept Domains exist in HL7?
Need to look at MIF ..
6.2.3.3
Create API for usage context querying ( i.e all that reference French Language).
All entities that we can enumerate, we need to add filter that includes supported type. (proposed)
Another reason to put conceptualdomain into the model.
6.2.3.4
Usage contexts - global.
Need ability to query the supportedttt
6.2.3.5
Returning the value domain defin and it's associated contexts.
Filter on value domain defin by concept domain
6.2.3.5.1
We already have is concept in value domain.
Create a convenience entity that iterates the use isEntityInDomain()
6.3.3.1
Create an entity inside the designated concept domain code system.
Create and maintain are same.
6.3.3.3
Create an entity - designated usage context code system
Loader for entities.
6.3.3.4
Jurisdictional Domain is considered "owner"
Business rule hook. Before executing any change requests, call this function and pass the insert/update, and the function would have some rules and decide yes or no.
·  Harolds Notes / Issue 1) Value Set Binding - association between an entity in the concept domain coding scheme and a value set
Issue 2) Rule set - the specification doesn't address how to create standard rule sets, which makes value sets non-standard and non-portable. We are going to propose (surprise) the same set of concrete rules that HL7 uses (and LexEVS w/ addition of a property. We will examine a 5th type of vdde - one that has a rule set URI + version identifer (?) and will discuss what the API to that might look like.
supportedConceptualDomain - local identifier
Should we consider a ConceptDomain Type? No answer
Question: how many concept domains are there in HL7 right now?
Note: Need to refer to the MIF model of bindings.
Designation part is covered by our pick list.
API to select entities by usage context (URI)
Need the ability to query the supported
Business rule hook -
·  / · 

LexEVS_20091202_MeetingNotes.doc Page 4 of 4 2/4/2010