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

Extension for Author (Roeland Luykx (RALY GmbH)) #172

Closed
ig-feedback opened this issue Sep 29, 2022 · 3 comments · Fixed by #186
Closed

Extension for Author (Roeland Luykx (RALY GmbH)) #172

ig-feedback opened this issue Sep 29, 2022 · 3 comments · Fixed by #186
Assignees
@ziegm
Labels
ready for telco STU 3 Comments/Issues from the Ballot for STU 3 (2022) Swiss IGs
Milestone
3.0.0 STU3 or nor...

Comments

@ig-feedback
Copy link
Collaborator

ch.fhir.ig.ch-core#2.1.0 /

In the IG for ch-emed and ch-vacd, there are extensions defined with the same meaning but for different resources.
Would it not be a good idea, to define a generic ch-core extension to be usable in different contexts?
see:

Roeland Luykx (RALY GmbH)
@oliveregger oliveregger added the STU 3 Comments/Issues from the Ballot for STU 3 (2022) label Sep 30, 2022
@ziegm
Copy link
Collaborator

ziegm commented Sep 30, 2022

In CH EMED is an open issue to change this extension: hl7ch/ch-emed#114
proposal: http://build.fhir.org/ig/hl7ch/ch-emed/branches/projectathon2022/StructureDefinition-ch-emed-ext-documentauthor.html

CH EMED: Reference(CH EMED PractitionerRole)
CH VACD: Reference(CH Core Patient | CH Core PractitionerRole | RelatedPerson)

@ziegm ziegm added this to the 3.0.0 STU3 or normative Ballot milestone Oct 11, 2022
ziegm added a commit that referenced this issue Oct 11, 2022
@ziegm
add extension ch-ext-author (issue #172)
5b669da
@ziegm ziegm linked a pull request Oct 11, 2022 that will close this issue
add extension ch-ext-author (issue #172) #186
Merged
@ziegm
Copy link
Collaborator

ziegm commented Oct 11, 2022 •
edited

Proposal to discuss @ telco:
Extension: Author of the content

Rücksprache mit Roeland, 11.10.: Er ist einverstanden mit dem Vorschlag.

@ziegm ziegm self-assigned this Oct 11, 2022
@ziegm
Copy link
Collaborator

ziegm commented Oct 12, 2022

Telco 12.10.2022:
Diskussion Konzepte 'Data Enterer' und 'Author of the content'. Unterschiedliche Kontexte, Gebrauch in Composition vs. MedStat/Disp/Req/Observation/Immunization.
Voting: 7-0-0

This was referenced Oct 12, 2022
Closed
Closed
@ziegm ziegm closed this as completed Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ziegm ziegm

Labels
ready for telco STU 3 Comments/Issues from the Ballot for STU 3 (2022) Swiss IGs
Projects
None yet
Milestone
3.0.0 STU3 or normative Ballot
Development

Successfully merging a pull request may close this issue.

add extension ch-ext-author (issue #172) hl7ch/ch-core
3 participants
@oliveregger @ziegm @ig-feedback