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

CH Core Coverage Profile - Proposal (Felizitas Wahl-Homner, CISTEC AG) #116

Closed
wahlfe opened this issue May 26, 2021 · 5 comments · Fixed by #286
Closed

CH Core Coverage Profile - Proposal (Felizitas Wahl-Homner, CISTEC AG) #116

wahlfe opened this issue May 26, 2021 · 5 comments · Fixed by #286

Comments

@wahlfe
Copy link

wahlfe commented May 26, 2021

Implementation Guide
ch.fhir.ig.ch-core#2.0.0 /StructureDefinition-ch-core-coverage.html

coverage.type
http://build.fhir.org/ig/hl7ch/ch-core/StructureDefinition-ch-core-coverage-definitions.html#Coverage.type
should have a binding on a swiss value set; attached proposal:

  • CISTEC_CodeSystem-CH-Core-HealthCoverageTypeCode-CodeSystem_20210526.xlsx

Please consider, to use the abbreviations OKP, UV, MV, etc. as proposed in the file, because it is common practice within the Swiss health system. Furthermore, the BfS-Code doesn't cover VVG/Zusatzversicherung for it isn't used within the BfS-statistics.

coverage.class.type
http://build.fhir.org/ig/hl7ch/ch-core/StructureDefinition-ch-core-coverage-definitions.html#Coverage.class.type
should have a binding on a swiss value set; attached proposal:

  • CISTEC_CodeSystem-CH-Core-HealthCoverageClasseCode-CodeSystem_20210526.xlsx

Please consider, to use the abbreviations A, HP, P as proposed in the file, because it is common practice within the Swiss health system. Furthermore, the BfS-Code doesn't provide enough codes for today's insurance coverages.

Kind regards
Felizitas Wahl-Homner
CISTEC AG

CISTEC_CodeSystem-CH-Core-HealthCoverageClassCode-CodeSystem_20210526.xlsx

CISTEC_CodeSystem-CH-Core-HealthCoverageTypeCode-CodeSystem_20210526.xlsx

@wahlfe wahlfe changed the title CH Core Coverage Profile - Proposal CH Core Coverage Profile - Proposal (Felizitas Wahl-Homner, CISTEC AG) May 26, 2021
@oliveregger
Copy link
Contributor

Abhängig von Entwicklungen auch in http://build.fhir.org/ig/hl7ch/ch-orf/StructureDefinition-ch-orf-coverage.html

@oliveregger
Copy link
Contributor

@oliveregger
Copy link
Contributor

oliveregger commented Nov 17, 2021

related also to hl7ch/ch-orf#80 (insert CH Related Person for Coverage)

@ziegm
Copy link
Collaborator

ziegm commented Apr 16, 2024

https://build.fhir.org/ig/hl7ch/ch-core/branches/issue116_coverage/StructureDefinition-ch-core-coverage.html

Proposal Coverage.type:

  • add CodeSystem-bfs-medstats-25-mainguarantor (to avoid introducing new codes) and CodeSystem-mainguarantor for the missing value, which is used also in CH ORF and other known use cases
  • CH ORF will update the codes according this change: Update Coverage (Michaela Ziegler, ahdis ag) ch-orf#177
  • image

Proposal Coverage.class.type:

  • use the already existing ValueSet-bfs-medstats-21-encountertype, to avoid introducing new codes
  • the proposed value "others" is not included
    • if there is an use case which has an additional value, it is possible to add ist, because the valueset binding is extensible
      • use a specific value for those use cases instead of others to be clear, what it is
  • image

ziegm added a commit that referenced this issue Apr 16, 2024
@ziegm ziegm linked a pull request Apr 16, 2024 that will close this issue
@ziegm ziegm added this to the v5.0.0-ballot milestone Apr 17, 2024
@ziegm
Copy link
Collaborator

ziegm commented Apr 24, 2024

24.04.2024 FHIR Telco:

  • discussion why using the BFS numbers
  • new introduced in CH Core (impact on CH ORF)
    • binding not required
  • discussion about "other" (included in one and not in the other)

Proposal for CH ORF

Vote: 13 - 0 - 1
Negative comment: seems like an adhoc solution, may there are international solutions, other resources would be use (e.g. InsurancePlan)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants