linuxforhealth / cdm-fhir-ig Goto Github PK

Add bindings to the coverage.relationship base element. Bindings may include WhPayer, Hipaa, HL7 and customer specific. Slicing would be one method of doing this.

Change excess_copay to excess-copay (underscore instead of hyphen).
Work with HI team to adjust mappings and update documentation.

IBM Watson Health references should change to IBM Health Data Connect in extension descriptions. Titles, in general, do not have this reference. Should this also include changing "wh-payer" references?

Default HL7 FHIR has Practitioner reference optional on PractitionerRole resource. Alverearie IG has Practitioner as required (1..1).

We have use cases for Marketscan where there is no additional data on the Practitioner. In these use cases, it would be beneficial to have PractitonerRole with no practitioner.

Canonical urls in the IG include the version number. See package.json (root folder).

This is not correct, and I think we should remove it.

• Discuss with team
• Remove the version

• Change the data type from decimal to integer
• Change any examples (ConditionInstanceWithNLPInsights)

Snapshot jar to be part of automated build process

• Create jar
• Version jar using iG version
• Include jar in site

Update codebase to compile with Sushi 1.x

• Convert IG to use Sushi 2.2
• Adjust automation build processes as needed

The link to the examples xml file is broken, has wrong file name.

Missing modifiers with 2 digit codes.

Improve descriptive text for key resources that need more explanation

• Patient match and other match profiles
• Patient attribution
• Others...

Add 2 new codes per Guild agreement on 1/6/2022

• #O "Other" "Other"
• #U "Unknown" "Unknown"

• Add an extension "major-diagnostic-category" to the Claim profile
• Add an extension "procedure-group" to the Claim profile

This is in support of WHWFFHCDM-287 jira ticket to define model extensions to support field & value level data quality and NLP insights.

Improve resource navigation

• Add map to resources, similar to FHIR HL7 resources page
• Finalize categories and review prototype with guild
• Publish changes

Change alias STANDARD-OCCUPATION-CODE to https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.7901# and only use as an example.

http://terminology.hl7.org/CodeSystem/soc has been retired.

Change CDM_Coverage_Instance example.
Verify no other uses in the IG.

Change the following:

• Replaced IBM >> HDC
• Replaced claro.com references >> acme.com
• Removed Outreach, IHE and Coordinate product branding
• Removed Watson references
• Removed Watson logo

Deferred, leave the following unchanged for now:

• Advantage / Advantage Suite branding text
• wh- prefixes, we are considering options for the new urls
• IBM urls, waiting for new url path

New identifier added as part of Drug claims

We believe we can remove the entire distributionManagement node from the pom.xml file.

Add commercial and health plan optional source fields to Coverage and InsurancePlan profiles

Add additional claims attributes to support HI Provider Directory

Releases page to be included in the IG:

• Add release notes page link to README.md
• Add release notes page link to IG index page
• Fix link on QA page (history)

Adopt FHIR F5 extension to support the course of a condition

To support clinical data ingestion, adding claim-type an extend the value set to include "financial". Typical values are professional, institutional or financial

Add automated releases tied to issues on the project board

• Releases tied to issues
• Release notes generated when release is created

TODOS

• Create automated release notes for issues tied to the issue tags
• Include build artifacts on tagged release (source code, snapshot jar, full-ig.zip, package.tgz)
• Add notes about gren release notes to history.md, which shows up on the IG in the history.html page (linked from QA report page)

We may need to incorporate changes to licensed codesets referenced in the IG.

• Guild to decide changes that need to be made
• Document changes required as issue details
• Implement IG changes

• Add "region-code" as an extension to the Coverage profile.
• Add "coverage-days" as an extension to the Coverage profile.
• Add "insurance-plan" as an extension to the Coverage profile.

Reduce number or warnings and errors on the IG QA page.

Update npm build scripts to work on Windows machines

Add downloads page to the IG, to include the following:

• Full-ig.zip
• Snapshot jar
• Package.tgz
• Zip files containing structure definitions

Publish build to github pages only on PR merge to main branch

• PRs under review should got though build process
• PRs under review should fail build if sushi cannot compile
• PRs under review should fail if publisher fails
• PRs under review should fail if snapshot build fails
• PRs under review SHOULD NOT publish to gh pages
• PRs SHOULD be published to gh pages on successful merge

We may need to add claim bundle profiles and examples to the IG

Update readme page to include information about release version numbering

• New major versions on breaking change

  • New required fields on existing profiles
  • Tighter cardinality restrictions on existing fields
  • Tighter data type or valueset binding constraints on existing profiles
  • Code changes to existing vocabularies
  • Url changes to existing profiles, vocabularies, etc.

• New minor version on non-breaking IG changes

  • New profiles or extensions
  • New codes, coding system, or vocabularies
  • Looser cardinality restrictions on existing fields
  • Looser data type or valueset binding constraints on existing profiles
  • New optional fields on existing profiles

• New revision on documentation changes that are reflected in the IG, including:

  • Changes to descriptions of profiles, extensions, or codes
  • Changes on IG pages that do not impact the profiles

• No version bump on other repo changes that do not affect the IG

  • Documentation in github pages only that are reflected in the IG (readme.md, etc)
  • Build CI changes

Update the home page to include the same licensing text that is on the README.md page

Add content to readme page

• Introduction describing the Alvearie IG
• Build Instructions
• Contribution Gude
• License
• Release History

std_place_cd was mapped to Claim.item.location.coding.code(set Claim.item.location.coding.system="http://terminology.hl7.org/CodeSystem/ex-serviceplace).

However, the HL7 code system does not have all of the values listed in "standard_place_of_service_desc.csv".

Look at adding the additional codes to "ServiceDeliveryLocationTypeValueSet" and reworking the Claim binding.

Improve usability of the process-meta-primary-or-secondary Code System with the following modifications:

1. Rename the  code system process-meta-primary-or-secondary" to process-meta-source-classification
2. Change the value of "primary" in this code system to "system-of-record" and the value of "secondary" to "derived"
3. Add an extension that is of data type "code" and associate it to the process-meta-source-classification ValueSet so that it can be nested under any derived field

Update IG to use alvearie base urls

• Remove all IBM urls from the IG
• Urls for structure definitons,

Replace urls with new base url http://linuxforhealth.org/fhir/cdm/

Ideally, vocabularies, etc should resolve to the new site

To support adding patient tokens for additional PII security:

• Create CDM Basic Resource
• Extend basic type codes
• Extend identifier type codes
• Add example

Add optional fields for Health Insights drug profiles

• Create branch
• Add extensions based on approved mappings for drug claim
• Add extensions base on approved mappings for drug claim response
• Update code systems, value sets
• Add examples
• Open PR & request review
• Review/correct review items
• Create release
• Increment major release version since it has breaking change
• Merge PR to main

Updated descriptive grammar in IG to shift focus from IBM to Alvearie