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

CH Core Composition Profile EPR (Michaela Ziegler (ahdis ag)) #97

Closed
ig-feedback opened this issue Mar 11, 2021 · 2 comments
Closed

CH Core Composition Profile EPR (Michaela Ziegler (ahdis ag)) #97

ig-feedback opened this issue Mar 11, 2021 · 2 comments
Labels
STU 1.2.0 Ballot Comments/Issues from the Ballot for STU2

Comments

@ig-feedback
Copy link
Collaborator

ig-feedback commented Mar 11, 2021 •
edited by ziegm
Loading

ch.fhir.ig.ch-core#1.2.0 /StructureDefinition-ch-core-composition-epr.html

What is the purpose of the Composition.identifier? Currently, the Composition.identifier and the Bundle.identifier have the same value (see example). Does that make sense?

Michaela Ziegler (ahdis ag)
@ziegm
Copy link
Collaborator

ziegm commented Mar 11, 2021

The format should be the same as the Bundle.identifier:
#95

@ziegm ziegm closed this as completed Mar 11, 2021
@ziegm ziegm reopened this Mar 11, 2021
@ziegm ziegm added the STU 1.2.0 Ballot Comments/Issues from the Ballot for STU2 label Mar 17, 2021
@oliveregger
Copy link
Contributor

fhir spec says:

A composition is a logical construct- its identifier matches to the CDA ClinicalDocument.setId.
http://hl7.org/fhir/composition.html#cda

Suggest to remove the EPR Set ID extension and restrict Composition.identifier to a uuid (see #95)

oliveregger added a commit that referenced this issue Mar 27, 2021
@oliveregger
remvoed ext setId, mapped to Comp.identifier #97
d4ba44c
@oliveregger oliveregger mentioned this issue Mar 27, 2021
Closed
@oliveregger oliveregger mentioned this issue Mar 27, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
STU 1.2.0 Ballot Comments/Issues from the Ballot for STU2
Projects
None yet
Milestone
No milestone
Development

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