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.

Sign up for GitHub

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

Jump to bottom

Procedure template does not map status to FHIR #9

Open
chaseastewart opened this issue Feb 27, 2024 · 0 comments
Open

Procedure template does not map status to FHIR #9

chaseastewart opened this issue Feb 27, 2024 · 0 comments
Labels
CDA->FHIR CDA to FHIR conversion

Comments

@chaseastewart
Copy link
Owner

chaseastewart commented Feb 27, 2024 •
edited
Loading

Communication status is fixed to completed which maps 1:1 to FHIR. In the event a different value is provided in the CDA, it'll be mapped forward.

fhir_converter/templates/ccda/Resource/_Communication.liquid

"status":"{{ communicationEntry.statusCode.code }}",

procedure-status needs to be mapped accordingly.

fhir_converter/templates/ccda/Resource/_Procedure.liquid

"status":"{{ procedureEntry.statusCode.code }}",
@chaseastewart chaseastewart mentioned this issue Feb 27, 2024
Open
@chaseastewart chaseastewart added the CDA->FHIR CDA to FHIR conversion label Feb 27, 2024
@chaseastewart chaseastewart changed the title Communication / Procedure templates do not map the status correctly to FHIR Communication / Procedure templates do not map the status to FHIR Feb 27, 2024
@chaseastewart chaseastewart changed the title Communication / Procedure templates do not map the status to FHIR Procedure templates do not map the status to FHIR Feb 27, 2024
@chaseastewart chaseastewart changed the title Procedure templates do not map the status to FHIR Procedure template does not map status to FHIR Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CDA->FHIR CDA to FHIR conversion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chaseastewart