Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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 join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant