Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.

ValueSets and Concept resource #4

Open
niquola opened this issue Sep 6, 2018 · 4 comments
Open

ValueSets and Concept resource #4

niquola opened this issue Sep 6, 2018 · 4 comments

Comments

@niquola
Copy link
Member

niquola commented Sep 6, 2018

We implemented FHIR terminology by introducing Concept resource, which can be represented in
database as a concept table.
For ValueSets effective expansions - valueset id's can be denormalized into concept as array of ids. This way expansion and lookup will be like:

select * 
  from concept 
  where valueSetIds contains "vs-1" and code in (...)
@niquola
Copy link
Member Author

niquola commented Sep 6, 2018

As well you can join concept table in your complex queries

@niquola
Copy link
Member Author

niquola commented Jan 13, 2019

Shell we discuss naming - spec says table should be named valueset_codes - i prefer Concept table name to be more FHIR-like resource name. The basic structure for this pseudo-resource can be taken from Coding data type.

@niquola
Copy link
Member Author

niquola commented Jan 13, 2019

valueset url and version naming should be normalised by FHIR conventions:

Concept.valueSet.url or Concept.valueSetURL ????

@niquola
Copy link
Member Author

niquola commented Jan 13, 2019

As well same Concept can participate in many valuesets - may be valueset cardinality can be * not 1 to 1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant