paynejd
commented
3 years ago Brainstorming new issues to be created for this epic: @snyaggarwal please review
Collection Versions and Expansions:
- Draft sample JSON for expansions and define default expansion parameters
- Implement new expansion resource
- Implement CRUD for expansions (using only default params)
- Implement custom parameters for expansions
- Change collection versions to only save the collection definition -- not the expansion
- Implement collectionVersion.expansion_url to enable "old_style" concept/mapping endpoints for a collectionVersion
- Implement collection.autoexpand_head and collectionVersion.autoexpand attributes, both defaulting to True to maintain backwards compatibility
- Implement expansion exports and the new collection version exports
References:
- Implement parameter to control whether and how OCL transforms a reference as it saves it in the definition -- default is
transform_reference="Versioned Resource, which is the "old style" behavior; out of the box, we also need to support "None" (related to #702) - Implement support for the following reference types:
- Individual concept/mapping (using resource version, source version, or version-less)
- Individual concept with cascade mappings option (cascade should be part of the expression, rather than a request parameter)
- Full ValueSet or CodeSystem
- All references above with support for OCL relative URLs or for FHIR canonical URLs
- Implement support for references that point to resources that are not defined in OCL
jamlung-ri
Implementing requirements that are laid out here: https://docs.google.com/document/d/1uhnnKxB_X_XLGeO7KSEN1obdL-UpkD82BraYE_ZpTzY/edit