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

Terminology binding in service request (Beat Heggli) #155

Closed
ig-feedback opened this issue Sep 20, 2023 · 3 comments
Closed

Terminology binding in service request (Beat Heggli) #155

ig-feedback opened this issue Sep 20, 2023 · 3 comments
Assignees
@pjolo
Labels
STU 2 Ballot

Comments

@ig-feedback
Copy link
Collaborator

ch.fhir.ig.ch-orf#2.0.0-ballot /

the terminology-binding in service_request (SNOMED-CT) should also be extended to CHOP code, as this is currently used

Beat Heggli
@ziegm
Copy link
Collaborator

ziegm commented Oct 18, 2023 •
edited

CHOP: hl7ch/ch-core#125

@pjolo
Copy link
Collaborator

pjolo commented Oct 23, 2023

We have no termonology binding to SNOMED CT in the service request profile.
SNOMED is only used as an example terminology. See image:

image

Definition of example binding: Instances are not expected or even encouraged to draw from the specified value set. The value set merely provides examples of the types of concepts intended to be included.

This means if necessary CHOP can also be used as terminology here.

@pjolo
Copy link
Collaborator

pjolo commented Nov 23, 2023

Beat Heggli was informed.

@pjolo pjolo closed this as completed Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pjolo pjolo

Labels
STU 2 Ballot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ziegm @ig-feedback @pjolo