profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/masnick/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Max Masnick masnick www.maxmasnick.com Epidemiologist, software developer

HL7/fhir-shc-vaccination-ig 21

FHIR Implementation Guide describing clinical and patient data contained within a SMART Health Card

masnick/combine 19

App for easy Stripe payments for invoices that you can host for free on Heroku

masnick/beautify-gem 8

Pretty output of Stata tables powered by Ruby

masnick/dotOSX 5

.files

chpir/SQL2Access 4

Run SQL commands saved in a text file in an Access database.

HL7/fhir-mCODE-ig 4

Minimal Common Oncology Data Elements Implementation Guide

chpir/offline_translation 3

Client-side JavaScript app for offline translations

masnick/census-blocks-in-urban-areas 3

Quick script to find all the US Census blocks in urban areas/urban clusters

chpir/DVS 2

Database validation server

chpir/KeyMaker 2

Visual Basic application that generates public/private key pairs (public project)

pull request commentHL7/fhir-shc-vaccination-ig

Add mmrv example

It seems like the most common use cases for requesting vaccinations will be:

  1. COVID only
  2. Full immunization history
  3. Multiple vaccines for an arbitrary set of diseases for international travel requirements (which practically could be better satisfied with 2️⃣ as the UX will be better than separate SHCs for each disease, or needing to get a single bespoke SHC issued for a specific set of diseases)

For 2️⃣ and 3️⃣, would it include each disease in type if separate https://smarthealth.cards#some-disease subtypes are defined for a large number of diseases? This could be unwieldy for implementers and would be redundant with the contents of the FHIR bundle. I also agree with Neelima's comments above about Verifiers being able to use the FHIR bundle contents rather than needing a disease-specific subtype for immunizations, and on the complexity in comprehensively mapping specific vaccines to diseases in the spec.

I also agree with the above comments on the difficulty of creating comprehensive sub-types of https://smarthealth.cards#laboratory.

Given this, I like the idea of not creating disease/lab-specific subtypes unless there is an overwhelmingly compelling use case (e.g., global pandemic).

For less common use cases, I think the approach Josh suggests using request semantics to make it possible to get a specific subset of https://smarthealth.cards#immunization or https://smarthealth.cards#laboratory makes sense. I think this will also scale better than highly granular subtypes for new SHC types that may come in the future.

jmandel

comment created time in a day

issue commentHL7/fhir-shc-vaccination-ig

Clean up description for manufactuer.identifier.eystem

The issue is this:

image

The short for system should read something like "namesapce of values identifying manufacturer". Currently it reads "Code identifying vaccine manufacturer", which is potentially confusing since system doesn't actually contain the code (value does).

masnick

comment created time in 3 days

issue openedHL7/fhir-shc-vaccination-ig

Clean up description for manufactuer.identifier.eystem

The definition for Immunization.manufacturer.identifer.system is 'code identifying vaccine manufacturer' - this is not a code, it's the namespace for the value that identifies it

created time in 4 days

issue openedHL7/fhir-shc-vaccination-ig

Add warning about relying on non-canonical lists of codes

e.g., for CVX, implementers should use https://www2a.cdc.gov/vaccines/iis/iisstandards/vaccines.asp?rpt=cvx to determine the list of valid codes.

created time in 9 days

issue closedHL7/fhir-shc-vaccination-ig

Canadian and UK SNOMED CT Vaccine Codes

Please consider adding ValueSets with the COVID-19 Vaccine Codes from the Canadian and UK SNOMED CT Editions:

https://browser.ihtsdotools.org/?perspective=full&conceptId1=28531000087107&edition=MAIN/SNOMEDCT-CA/2021-03-31&release=&languages=en,fr

https://termbrowser.nhs.uk/?perspective=full&conceptId1=39330711000001103&edition=uk-edition&release=v20210512&server=https://termbrowser.nhs.uk/sct-browser-api/snomed&langRefset=999001261000000100,999000691000001104

closed time in 22 days

igorsirkovich

issue commentHL7/fhir-shc-vaccination-ig

Canadian and UK SNOMED CT Vaccine Codes

@igorsirkovich We were able to get the Canadian edition of SNOMED explicitly included in the STU1 ballot version of the IG: http://hl7.org/fhir/uv/shc-vaccination/2021Sep/ValueSet-vaccine-snomed.html

We are limited to the SNOMED editions that tx.fhir.org supports, which does not currently include UK SNOMED. But now that we have a working method for including specific SNOMED editions, we will continue to update the IG whenever possible with the full suite of SNOMED editions.

igorsirkovich

comment created time in 22 days

pull request commentHL7/fhir-mCODE-ig

Laterality - FHIR-32340

TreatmentIntentVS is a broken link on https://build.fhir.org/ig/HL7/fhir-mCODE-ig/branches/laterality/group-treatment.html -- not sure what change caused this, but it looks ok on the STU2 ballot build.

image

saulakravitz

comment created time in 22 days

Pull request review commentHL7/fhir-mCODE-ig

Laterality - FHIR-32340

 Description: "Anatomic volume for John Anyperson's brachytherapy." * patient = Reference(cancer-patient-john-anyperson) * description = "Structure of lower lobe of left lung" * location = SCT#31094006  "Structure of lobe of lung (body structure)"-* locationQualifier[0] = SCT#7771000 "Left (qualifier value)"-* locationQualifier[1] = SCT#261122009 "Lower (qualifier value)"-+// * locationQualifier[0] = SCT#7771000 "Left (qualifier value)"+// * locationQualifier[1] = SCT#261122009 "Lower (qualifier value)"

I would remove the commented-out lines before merging, or add a prose explanation for why they remain.

saulakravitz

comment created time in 22 days

PullRequestReviewEvent
PullRequestReviewEvent

push eventHL7/fhir-mCODE-ig

Max Masnick

commit sha 5e105aa7167031f04155a638fdb0c4c2ef7f2807

Additional tweak

view details

push time in 24 days

PR opened HL7/fhir-mCODE-ig

Edits to profile conformance page

Minor edits to try to improve clarity.

+13 -9

0 comment

1 changed file

pr created time in 24 days

create barnchHL7/fhir-mCODE-ig

branch : oti-edits

created branch time in 24 days

created tagHL7/fhir-shc-vaccination-ig

tagv0.6.2

FHIR Implementation Guide describing clinical and patient data contained within a SMART Health Card

created time in a month

push eventdvci/JIRA-Spec-Artifacts

Max Masnick

commit sha 3941fe3bfe67aae48cecfa9f9bd43940543b9413

Deprecate 0.6.0

view details

push time in a month

PR opened HL7/JIRA-Spec-Artifacts

Update FHIR-shc-vaccination.xml

We were missing some pages.

Also I properly deprecated 0.6.0 (which doesn't have a permanent published location as it was just the proposed ballot version).

+52 -37

0 comment

1 changed file

pr created time in a month

push eventdvci/JIRA-Spec-Artifacts

Max Masnick

commit sha b1beb4af3abf9c2d36bbe839ec0676f6d8372e68

Update FHIR-shc-vaccination.xml

view details

push time in a month

create barnchHL7/fhir-shc-vaccination-ig

branch : main

created branch time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha dd74ec11c5ebf7ddbf8cba3ed9341eb822f11734

Remove extra entry from package-list, fix link in README

view details

push time in a month

pull request commentHL7/JIRA-Spec-Artifacts

Fix CI build URL and add version

For now, you'll need to push your content to 'master'. The official CI build can't be at 'master'.

@lmckenzi -- I switched the URLs here to work with master. Please change our repo to use master as the default branch. Thanks!

masnick

comment created time in a month

create barnchHL7/fhir-shc-vaccination-ig

branch : master

created branch time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha cca8031dcd61883c5ca181fbef9bae71d46571ca

Move to master as default branch to support CI build See https://github.com/HL7/JIRA-Spec-Artifacts/pull/253

view details

push time in a month

push eventdvci/JIRA-Spec-Artifacts

Max Masnick

commit sha 4da901c59587b7c0e716317ff8a3f4b1ec3076fe

Move to master branch

view details

push time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha 384451b82589a4a63e460b71fef9d3ba43040941

0.1.0

view details

push time in a month

create barnchHL7/fhir-shc-vaccination-ig

branch : 0.1.0

created branch time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha 7dd85ff83ca3fb306637dc4698168b7b4e6b565e

Change build label to reflect this is the ballot version

view details

push time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha cfcfcbe75ed3d04e7b2e18b7ac6f8100e2ca8e5b

Update package list and Jira XML file

view details

Max Masnick

commit sha 2e4092268ad45a5517b73494bd268e6c5cb46da1

Fix copyrights on value sets and correct ICD11 URI

view details

Max Masnick

commit sha 27fa492e2ca447637a4d3b11df1080b7cbc3dfdb

Update IG copyright and bump version to 0.6.2

view details

Max Masnick

commit sha 5bf87fbd69bbc350185e15c8e9b299a85af42e2a

Update some instances of ICD11 URIs I missed in the previous commit

view details

Max Masnick

commit sha d571261bf269c8e5b00548f2bf7b6bd1daeea7b1

Merge branch 'dev' into main

view details

push time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha 5bf87fbd69bbc350185e15c8e9b299a85af42e2a

Update some instances of ICD11 URIs I missed in the previous commit

view details

push time in a month

push eventHL7/fhir-shc-vaccination-ig

Max Masnick

commit sha cfcfcbe75ed3d04e7b2e18b7ac6f8100e2ca8e5b

Update package list and Jira XML file

view details

Max Masnick

commit sha 2e4092268ad45a5517b73494bd268e6c5cb46da1

Fix copyrights on value sets and correct ICD11 URI

view details

Max Masnick

commit sha 27fa492e2ca447637a4d3b11df1080b7cbc3dfdb

Update IG copyright and bump version to 0.6.2

view details

push time in a month

PR opened HL7/JIRA-Spec-Artifacts

Fix CI build URL and add version

The CI build doesn't recognize main as the default branch name, so I updated the URL to manually include /branch/main so the links won't be broken.

I also added 0.6.2 which is the version we will go to ballot with. Our proposed ballot version was 0.6.0, and subsequent QA changes led to incrementing the version number twice.

+4 -3

0 comment

1 changed file

pr created time in a month