This wiki has undergone a migration to Confluence found Here
Difference between revisions of "II WGM Agenda January 2018"
Jump to navigation
Jump to search
| (8 intermediate revisions by 2 users not shown) | |||
| Line 69: | Line 69: | ||
* Antitrust rules. | * Antitrust rules. | ||
2. General Administration | 2. General Administration | ||
| − | * Review [https://gforge.hl7.org/gf/download/frsrelease/ | + | * Co-chair election |
| − | * Review [https://gforge.hl7.org/gf/download/frsrelease/1255/16076/SSD_SD-WorkGroupHealth_2018JanInterim.pdf Workgroup Health Metrics ( | + | * Review [https://gforge.hl7.org/gf/download/frsrelease/1260/16160/PBS_Metrics_20180115_2018JanWGM.xlsx PBS Metrics (final)] |
| + | * Review [https://gforge.hl7.org/gf/download/frsrelease/1255/16076/SSD_SD-WorkGroupHealth_2018JanInterim.pdf Workgroup Health Metrics (final)] | ||
| + | * Review and re-affirm SWOT [http://www.hl7.org/documentcenter/public/wg/imagemgt/IIWG%20SWOT%20Analysis%20201510.docx (link)] | ||
* Update of all [http://www.hl7.org/special/committees/projman/searchableprojectindex.cfm?sortBy=&sortDirection=&FilterKeyword=&FilterProjectNumber=&FilterProjectSponsor=Imaging+Integration+Work+Group&FilterProjectType= Project] Deadlines | * Update of all [http://www.hl7.org/special/committees/projman/searchableprojectindex.cfm?sortBy=&sortDirection=&FilterKeyword=&FilterProjectNumber=&FilterProjectSponsor=Imaging+Integration+Work+Group&FilterProjectType= Project] Deadlines | ||
| − | * Review items for 3 year plan - [http://www.hl7.org/special/committees/projman/searchableprojectindex.cfm?sortBy=&sortDirection=&FilterKeyword=&FilterProjectNumber=&FilterProjectSponsor=Imaging+Integration+Work+Group&FilterProjectType=&FilterStatus=3-Year+Plan+Item Project] Index | + | * (deferred) Review items for 3 year plan - [http://www.hl7.org/special/committees/projman/searchableprojectindex.cfm?sortBy=&sortDirection=&FilterKeyword=&FilterProjectNumber=&FilterProjectSponsor=Imaging+Integration+Work+Group&FilterProjectType=&FilterStatus=3-Year+Plan+Item Project] Index |
| − | |||
* Review any other housekeeping topics | * Review any other housekeeping topics | ||
3. Use of media in FHIR | 3. Use of media in FHIR | ||
| Line 103: | Line 104: | ||
* FHIR-I | * FHIR-I | ||
* OO | * OO | ||
| + | ** Project status of 1343 (Eye Care and Opthalmalogy on FHIR) | ||
| + | ** Project status of 682 (Specimen CMET) | ||
| + | ** Project status of 1010 (Ordering service interface spec) | ||
| + | ** Project status of 862 (Unique Specimen Identifier Requirements) | ||
| + | ** Use of Media in FHIR | ||
* CIMI | * CIMI | ||
* ISO/TC 215 WG-2 | * ISO/TC 215 WG-2 | ||
| Line 108: | Line 114: | ||
* Release4 Activities (e.g., action items, Ballot Prep activities) | * Release4 Activities (e.g., action items, Ballot Prep activities) | ||
* Tasks requested by FHIR-I | * Tasks requested by FHIR-I | ||
| + | * Incorporate workflow abstractions based on Lloyd's report | ||
| + | # Unresolved list: | ||
| + | ## Warning: The element ImagingStudy.basedOn excludes the following type(s) that are part of the pattern: Reference(Appointment), Reference(AppointmentResponse), Reference(Claim), Reference(CommunicationRequest), Reference(Contract), Reference(DeviceRequest), Reference(EligibilityRequest), Reference(EnrollmentRequest), Reference(ImmunizationRecommendation), Reference(MedicationRequest), Reference(NutritionOrder), Reference(ProcessRequest), Reference(Task), Reference(SupplyRequest), Reference(VisionPrescription). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.procedureCode has a name that differs from the workflow element it maps to: code. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.procedureCode has increased the maximum cardinality from 1 to *. Is it in the 80% for this element to repeat? Is there a need to change the workflow pattern? Please discuss with the workflow project. | ||
| + | ## Warning: The resource ImagingStudy has multiple elements that map to pattern element Event.identifier: . If this is because different elements are used for different types or because the resource embeds the concept of multiple Events, then add to the ignore list. Otherwise, determine which element should actually be mapped. | ||
| + | ## Warning: The element ImagingStudy.uid has a name that differs from the workflow element it maps to: identifier. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.uid includes the following type(s) that are not part of the pattern: oid. If the types should be considered for addition to the pattern, contact the FHIR Workflow project. Otherwise, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.uid has increased the minimum cardinality from 0 to 1. Verify that it's reasonable to make this element mandatory for all possible use-cases. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.accession has a name that differs from the workflow element it maps to: identifier. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.uid has a name that differs from the workflow element it maps to: identifier. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.uid includes the following type(s) that are not part of the pattern: oid. If the types should be considered for addition to the pattern, contact the FHIR Workflow project. Otherwise, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.uid has increased the minimum cardinality from 0 to 1. Verify that it's reasonable to make this element mandatory for all possible use-cases. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.instance.uid has a name that differs from the workflow element it maps to: identifier. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.instance.uid excludes the following type(s) that are part of the pattern: Identifier. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.instance.uid includes the following type(s) that are not part of the pattern: oid. If the types should be considered for addition to the pattern, contact the FHIR Workflow project. Otherwise, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.series.instance.uid has increased the minimum cardinality from 0 to 1. Verify that it's reasonable to make this element mandatory for all possible use-cases. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.location, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.note, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The resource ImagingStudy has multiple elements that map to pattern element Event.occurrence[x]: . If this is because different elements are used for different types or because the resource embeds the concept of multiple Events, then add to the ignore list. Otherwise, determine which element should actually be mapped. | ||
| + | ## Warning: The element ImagingStudy.started excludes the following type(s) that are part of the pattern: Period, Timing. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Error: The element ImagingStudy.started has a w5 mapping of 'when.init' which disagrees with the Event pattern mapping of 'when.done'. Either the element has the wrong workflow mapping, the element has the wrong w5 mapping or there's a problem with the pattern's w5 mapping. If you're not sure what to fix, please discuss with the Workflow project. | ||
| + | ## Warning: The element ImagingStudy.series.started excludes the following type(s) that are part of the pattern: Period, Timing. If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.procedureReference has a name that differs from the workflow element it maps to: partOf. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.procedureReference excludes the following type(s) that are part of the pattern: Reference(ChargeItem), Reference(ClaimResponse), Reference(ClinicalImpression), Reference(Communication), Reference(Composition), Reference(Condition), Reference(Consent), Reference(Coverage), Reference(DeviceUseStatement), Reference(DiagnosticReport), Reference(DocumentManifest), Reference(DocumentReference), Reference(EligibilityResponse), Reference(Encounter), Reference(EnrollmentResponse), Reference(EpisodeOfCare), Reference(ExplanationOfBenefit), Reference(FamilyMemberHistory), Reference(GuidanceResponse), Reference(ImagingStudy), Reference(Immunization), Reference(MeasureReport), Reference(Media), Reference(MedicationAdministration), Reference(MedicationDispense), Reference(MedicationStatement), Reference(Observation), Reference(PaymentNotice), Reference(PaymentReconciliation), Reference(ProcessResponse), Reference(QuestionnaireResponse), Reference(RiskAssessment), Reference(SupplyDelivery), Reference(Task). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.performer, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.performer.actor, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.performer.function, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The element ImagingStudy.reason has a name that differs from the workflow element it maps to: reasonCode. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.reasonReference, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.status, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The resource ImagingStudy does not have an element with a mapping to the Event pattern element Event.statusReason, nor is it listed as a context in the corresponding extesnsion. Possibilities: mapping was missed; element is in the 80% and should be added and mapped; element is outside the 80% but should be supported by the standard pattern extension; element is not relevant and this warning should be added to the 'workflow-warning-ignore' file | ||
| + | ## Warning: The element ImagingStudy.patient has a name that differs from the workflow element it maps to: subject. Confirm that this inconsistency is intentional and is believed to better help domain implementers understand the purpose of the element in context. If so, add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Warning: The element ImagingStudy.patient excludes the following type(s) that are part of the pattern: Reference(Group). If the pattern types fall within the 80% for the resource, then add them, otherwise add this warning to the 'workflow-warning-ignore' file. | ||
| + | ## Error: The element ImagingStudy.series.performer has a workflow mapping of Event.performer.agent which is an element that doesn't exist in the Event pattern | ||
| + | # Resolved list: | ||
| + | ## N/A | ||
| + | 8. Review WG-6 presentations and outcomes | ||
|- | |- | ||
|Q4 3:30pm | |Q4 3:30pm | ||
|'''II/WG-20''' | |'''II/WG-20''' | ||
|Newberry – 3rd Floor | |Newberry – 3rd Floor | ||
| − | | | + | |9. Book follow-up meetings and confirm May WGM for II |
| − | + | 10. Continue FHIR Topics | |
| − | + | ||
| − | + | 11. WIA / MHD-I discussion | |
| + | |||
| + | 12. DICOM thumbnails | ||
|-border="4" cellpadding="8" style="background:#f0f0f0;" | |-border="4" cellpadding="8" style="background:#f0f0f0;" | ||
|. |||||||| | |. |||||||| | ||
| Line 158: | Line 206: | ||
|'''II/WG-20 hosting DICOM WG-10''' | |'''II/WG-20 hosting DICOM WG-10''' | ||
|Newberry – 3rd Floor | |Newberry – 3rd Floor | ||
| − | | | + | |13. Co-chair election results |
| − | + | 14. WG-10 topics | |
|- | |- | ||
| rowspan="2" | Q2 11:00am | | rowspan="2" | Q2 11:00am | ||
| Line 173: | Line 221: | ||
|'''II/WG-20 hosting DICOM WG-10''' | |'''II/WG-20 hosting DICOM WG-10''' | ||
|Newberry – 3rd Floor | |Newberry – 3rd Floor | ||
| − | |? | + | |15. Cover any remaining topics for II / WG-20 |
| + | * Review items for 3 year plan - [http://www.hl7.org/special/committees/projman/searchableprojectindex.cfm?sortBy=&sortDirection=&FilterKeyword=&FilterProjectNumber=&FilterProjectSponsor=Imaging+Integration+Work+Group&FilterProjectType=&FilterStatus=3-Year+Plan+Item Project] Index | ||
|- | |- | ||
|Q4 3:30pm | |Q4 3:30pm | ||
| − | |'''II/WG-20''' | + | |'''II/WG-20 hosting DICOM WG-10''' |
|Newberry – 3rd Floor | |Newberry – 3rd Floor | ||
| − | | | + | |? |
|- | |- | ||
|-border="4" cellpadding="8" style="background:#f0f0f0;" | |-border="4" cellpadding="8" style="background:#f0f0f0;" | ||
| Line 186: | Line 235: | ||
|Q1 9:00am | |Q1 9:00am | ||
|'''II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2''' | |'''II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2''' | ||
| − | | | + | |Camp – 3rd Floor |
| − | |||
| − | |||
|? | |? | ||
|- | |- | ||
|Q2 11:00am | |Q2 11:00am | ||
|'''II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2''' | |'''II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2''' | ||
| − | | | + | |Camp – 3rd Floor |
| − | |||
| − | |||
|? | |? | ||
|- | |- | ||
|Q3 1:45pm | |Q3 1:45pm | ||
|'''II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2''' | |'''II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2''' | ||
| − | | | + | |Camp – 3rd Floor |
| − | |||
| − | |||
|? | |? | ||
|- | |- | ||
Latest revision as of 22:55, 30 January 2018
Imaging Integration WG Agenda - HL7 WGM 01/2018 New Orleans
Agenda
| Day | Quarter | Event | Room | Topics |
| Sunday 28th | Q1 9:00am | No meeting | ||
| Q2 11:00am | No meeting | |||
| Q3 1:45pm | No meeting | |||
| Q4 3:30pm | No meeting | |||
| . | ||||
| Monday 29th | Q1 9:00am | No meeting | ||
| Q2 11:0am | No meeting | |||
| Q3 1:45pm | No meeting | |||
| Q4 3:30pm | FHIR Infrastructure hosting II | Commerce – 3rd Floor | Agenda | |
| . | ||||
| Tuesday 30th | Q1 9:00am | II/WG-20 | Newberry – 3rd Floor |
1. Opening
2. General Administration
3. Use of media in FHIR |
| Q2 11:00am | II/WG-20 | Newberry – 3rd Floor | 4. Projects
5. Review open list of tracker items
| |
| Q3 1:45pm | II/WG-20 | Newberry – 3rd Floor | 6. Review joint meeting agendas
7. FHIR Topics
8. Review WG-6 presentations and outcomes | |
| Q4 3:30pm | II/WG-20 | Newberry – 3rd Floor | 9. Book follow-up meetings and confirm May WGM for II
10. Continue FHIR Topics 11. WIA / MHD-I discussion 12. DICOM thumbnails | |
| . | ||||
| Wednesday 31th | Q1 9:00am | II/WG-20 hosting DICOM WG-29 | Newberry – 3rd Floor | WG-29 Meeting Folder |
| II/WG-20 Reps to BR&R | Marlborough - 2nd Floor | ? | ||
| Q2 11:00am | Orders and Observations hosting II | Kabacoff – Riverside Bldg | ? | |
| WG-29 | Newberry – 3rd Floor | WG-29 Meeting Folder | ||
| Q3 1:45pm | II/WG-20 hosting DICOM WG-29 | Newberry – 3rd Floor | WG-29 Meeting Folder | |
| Q4 3:30pm | II/WG-20 hosting FHIR Infrastructure | Newberry – 3rd Floor | FHIR-I Agenda | |
| . | ||||
| Thursday 1st | Q1 9:00am | Structured Docs hosting II (Reps only) | ? | ? |
| II/WG-20 hosting DICOM WG-10 | Newberry – 3rd Floor | 13. Co-chair election results
14. WG-10 topics | ||
| Q2 11:00am | II/WG-20 Reps to CIMI | Newberry – 3rd Floor | ? | |
| WG-29 hosting DICOM WG-10 | Newberry – 3rd Floor | ? | ||
| Q3 1:45pm | II/WG-20 hosting DICOM WG-10 | Newberry – 3rd Floor | 15. Cover any remaining topics for II / WG-20
| |
| Q4 3:30pm | II/WG-20 hosting DICOM WG-10 | Newberry – 3rd Floor | ? | |
| . | ||||
| Friday 2nd | Q1 9:00am | II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2 | Camp – 3rd Floor | ? |
| Q2 11:00am | II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2 | Camp – 3rd Floor | ? | |
| Q3 1:45pm | II/WG-20 hosting DICOM WG-10, ISO/TC 215 WG-2 | Camp – 3rd Floor | ? | |
| Q4 3:30pm | No meeting | N/A | N/A |
