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

Correct process to add to and move around Codeable Concept data? #41

Open
RicLund opened this issue Feb 6, 2019 · 2 comments
Open

Correct process to add to and move around Codeable Concept data? #41

RicLund opened this issue Feb 6, 2019 · 2 comments

Comments

@RicLund
Copy link

RicLund commented Feb 6, 2019

We've added some of the Codeable Concept types and values which the accelerator did not yet cover - for example Consent Scope - https://www.hl7.org/fhir/valueset-consent-scope.html.

What would you recommend as the best way to move the CC values through our environments as part of our DevOps processes? We are likely to add more as we continue to use and extend the accelerator.

Thanks!

@RicLund
Copy link
Author

RicLund commented Feb 6, 2019

I see I can use CDM.HealthAccelerator.ExportCodeableConcepts to export the Option Set but it doesn't seem to export the data from the Codeable Concept entity into a separate file? If it did I could use CDM.HealthAccelerator.ImportCodeableConcepts to bring both into my second instance. Am I missing something? Is there a reason the CC data doesn't export?

@mgernaey
Copy link
Contributor

mgernaey commented Feb 8, 2019

HI Sorry for the delay. It actually does generate the separate file with the names and linkage so its possible. I thought the instructions stated how, but let me review and get back to you by the morning.

Cheers!!

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

2 participants