Value Set evaluation by HTA across product families
This activity seeks to identify process and mapping requirements and requires the following steps
- Identify if the notion is across families or not (if used in more than one family member we need to consider it). This includes identification of potential matching or similar semantic space content.
- Identify synonyms and the level of equivalence
- Review value set content from each family member
- Establish method of mapping
Consider metadata and tooling issues and publishing requirements to harmonize.
Simple (no hierarchy, no flavors of null, seemingly 1:1 concepts)
V2 table # and name / V3 Value Set/s / CDA value set/s / FHIR value set/s / Issues:0007 Admission type
- A Accident
- E Emergency
- L Labor and Delivery
- R Routine
- N Newborn (Birth in healthcare facility)
- U Urgent
- C Elective
- E (emergency)
- LD (labor and delivery)
- NB (newborn)
AdmissionTypeQSRS
25876001 / Emergency
103391001 / Urgent
103390000 / Elective
46068001 / Newborn
25809009 / Trauma victim[JTC1]
/ 1.14.2.1.189 Encounter-admit-source[JTC2]
Hosp-trans - Transferred from mother hospital
Emd - from accident/emergency department
Outp - from outpatient department
Born - born in hospital
gp - general practiioner referral
mp - medical practitioner / physician referral (HG assumed not a GP)
nursing - from nursing home
psych - from psychiatric hospital
rehab - from rehabilitation facility
other - other / A similar concept domain seems to be covered by some codes in ActReason. There is no exact match to the v3 concept domain, whose meaning is unclear, as the Domain is missing a definition in v3 to match against the table definition in v2 and the field definitions it is used for.
? is semantic space
- place/dept through which admission occurred
- Reason or service type for which they were admitted
- Priority of admission
- Some realm specific statistical counter
- Other?
0017 Transaction type
0027 Priority
0065 Specimen action code
0080 Nature of abnormal testing
0112 Discharge disposition / Uses SNOMED CT
Called discharge location type
74964007 / other - qualifier
306205009 / Referral to hospice
306689006 / Discharge to Home
306694006 / Discharge to nursing home
306700000 / Discharge to long stay hospital
429202003 / Transfer of care to hospital
445060000 / Left against medical advice
/ 1.14.2.1.190 encounter-discharge-disposition
home / Home
other-hcf / Other healthcare facility
hosp / Hospice
long / Long-term care
aadvice / Left against advice
exp / Expired
psy / Psychiatric hospital
rehab / Rehabilitation
oth / Other
0145 Room type
0165 Administration method
0806 Sterilization type
Small complexity (hierarchy, no flavors of null, seemingly 1:1 concepts)
V2 table # and name / V3 Value Set/s / CDA Value set/s / FHIR value set/s0078 Interpretation codes
0514 Transfusion adverse reaction
0725 Mood codes
Some complexity (no hierarchy, seemingly 1:1 concepts, flavors of null included)
V2 table # and name / V3 Value Set/s / CDA Value set/s / FHIR value set/s0001 Administrative sex
0066 Employment status
0004 Patient class
0006 Religion
0425 Newborn code
More complexity (hierarchy, flavors of null, but seemingly 1:1 concepts)
V2 table # and name / V3 Value Set/s / CDA Value set/s / FHIR value set/s0002 Marital status
Complex (hierarchy, flavors of null, n:n concept relationships)
V2 table # and name / V3 Value Set/s / CDA Value Set/s / FHIR value set/s0487 Specimen type
[JTC1]This is interesting as it is a semantically incongruent set. Three of the values are qualifiers and two are findings. Findings are certainly not consistent with the meaning of the field as they are related to the patient, not the type of admission. This is a clear example of choosing content based on “words” rather than meaning.
[JTC2]This set of terms does not appear to be in the same context as the other value sets as they refer to transfers rather than sources.