OCL evaluates references (#1854) to create an expansion of a repository (specifically one that has a collection aspect). Similar to references, expansions are tied to a particular version of the repository.
An expansion is an evaluation of the references (i.e. instructions) at a point in time.
Expansions are what actually contain a collection’s concepts and mappings.
You can make lots of expansions out of one set of references.
Example: I made a collection expansion for Smoking Status from CIEL a few months ago, but CIEL updated the concept. How do I get updates to the content I’m using? Make another expansion!
Note: Expansions can be a confusing idea because users are often not mentally separating the ideas of references (the instructions on how to make an expansion) from the expansions, and expansions from the collection versions themselves (since collections are a container for both the references and the expansions). Many users are not aware that there is an expansion that drives how their collection works. This is fine for less advanced users, but advanced users like FHIR terminology managers are very keen on seeing the collection's (possibly many) expansions and the different results between them.
User Stories:
As a consumer, I want to view list of references and parameters of an expansion and the results (eg concepts, mappings) of evaluating those references so that I can understand and potentially recreate how the contents of this repository was evaluated.
As an implementer/adapter, I want to create a new expansion for my repository several months after its first evaluation so that I can re-evaluate the results of my repo and see if the new results are of interest to me.
As an implementer/adapter, I want to recreate an expansion using the same parameters (e.g. source version, timeframe, etc.) in a different collection that uses a different set of references so that I can be consistent with my expansions when I have created a new repo version (which includes different references than previous versions).
OCL evaluates references (#1854) to create an expansion of a repository (specifically one that has a collection aspect). Similar to references, expansions are tied to a particular version of the repository.
Note: Expansions can be a confusing idea because users are often not mentally separating the ideas of references (the instructions on how to make an expansion) from the expansions, and expansions from the collection versions themselves (since collections are a container for both the references and the expansions). Many users are not aware that there is an expansion that drives how their collection works. This is fine for less advanced users, but advanced users like FHIR terminology managers are very keen on seeing the collection's (possibly many) expansions and the different results between them.
User Stories: