Difference between revisions of "MnM Minutes CC 20150319"
(Created page with "{{subst::MnM Template for Agenda-Minutes}}") |
|||
Line 1: | Line 1: | ||
− | + | [[Category:2015 MnM Minutes]] | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
__NOTOC__ | __NOTOC__ | ||
− | =M&M Conference Call | + | =M&M Conference Call 1:00PM Eastern Time (Date above)= |
− | |||
[[:Category:2015 MnM Minutes|Return to MnM Minutes]] | [[:Category:2015 MnM Minutes|Return to MnM Minutes]] | ||
==Agenda== | ==Agenda== | ||
− | *Approve [[ | + | *Approve [[MnM_Minutes_CC_20150312| Minutes Prior Meeting on 03/12]] |
+ | |||
==Attendees== | ==Attendees== | ||
− | *??? ( | + | *Lloyd McKenzie (chair) |
− | * | + | *Austin Kreisler |
+ | *Gordon Raup | ||
+ | *Chad Armstrong | ||
+ | *Daniel Lanphear | ||
+ | *Mark Kramer | ||
+ | |||
+ | ==Minutes== | ||
+ | Approved minutes of 03/12 | ||
+ | :Austin/Daniel 5-0-0 | ||
+ | |||
+ | ==Block votes== | ||
+ | *FHIR Core block vote: | ||
+ | :5866: Split $meta-change into $add-meta and $delete-meta | ||
+ | :5818: DataElement should use ElementDefinition | ||
+ | :3903: Conformance searchParam are not 'additional' | ||
+ | :3889: errors in standard extensionDefinitions | ||
+ | :3858: Need to define behavior around ignoring updates | ||
+ | :3830: Clarify effect of deletion on resource history | ||
+ | :3821: Add code system manifest to ValueSet expansion | ||
+ | :3761: Clarification of how to implement search on boolean fields (e.g. Patient.active) | ||
+ | :3744: Create operation - should the effects of idempotence be described? | ||
+ | :3740: The list of FHIR datatypes should be explicit about "element" and derived types | ||
+ | :3694: ConceptMap.name should be 0..1 | ||
+ | :3692: Remove type idref | ||
+ | :3664: Profile definition for "Any" | ||
+ | :3591: Versionless updates should be permitted | ||
+ | :3522: Extensibility page has incorrect example for modifier, and has xml-specific language | ||
+ | :3516: Document what the 'lock' icon means in the xml comments | ||
+ | :3504: Can extensions have values and sub-extensions? | ||
+ | :3468: Tool extensions should be moved to resource-specific profiles | ||
+ | :3235: Example name guidance | ||
+ | :3342: contained resources overrepresented in examples | ||
+ | :3807: Should add rationale to Invariant | ||
+ | :3802: Specify what it means for a search parameter to matches a complex datatype | ||
+ | :3773: Other needs to be renamed | ||
+ | :3650: Clarify format of Profile.extensionDefn.context | ||
+ | :3381: Objective-C Reference Implementation from Download page is broken | ||
+ | :3835: Rename keyword "metadata" to "_metadata" (Propose to reject this) | ||
+ | :3859: add clarifying text for Profile.x.element.type.profile (Propose to reject this - something similar in intent but different in details done as part of StructureDefinition change) | ||
+ | :3860: REST Search syntax clarification | ||
+ | :3873: Explicitly specify resource/element types throughout? (Note: this one won't be applied to later, it's a massive change, but it's definitely needed to be done) | ||
+ | :3880: extension content model example change request | ||
+ | :3890: consistent use of 'any' for extensionDefinitions | ||
+ | :3901: ;in should be :not? | ||
+ | :3906: Broken Links | ||
+ | :3910: Separate the updateCreate Resource property into an updat and create values | ||
+ | :3924: Add clarification on case sensitivity in search vs validation | ||
+ | :3928: Make parameter types hyperlinks | ||
+ | :3933: Parameter resource does not support parts that are resources | ||
+ | :5219: Fix cardinality of Narrative structure | ||
+ | :5236: fix typo in example | ||
+ | :5242: Jan 2015 Ballot Comment #119 (refer to extension registry) | ||
+ | :5289: Jan 2015 Ballot Comment #168 - improve documentation about group and list | ||
+ | :5311: Jan 2015 Ballot Comment #190 (move narrative about profiles) | ||
+ | :5513: Ambiguous operation $validate | ||
+ | :5601: Add an explicit specification of the resource identifier | ||
+ | :5605: Unclear how to know what filters a given system supports for a given code system | ||
+ | :5780: FHIR id definition is inconsistent | ||
+ | :5796: Prohibit versionId and lastUpdated for contained resources | ||
+ | :5816: Update documentation about extensions in compartments | ||
+ | :5837: Additional issue types for warnings | ||
+ | :5851: "Binding can only be present for coded elements" needs to be updated on DataElement | ||
+ | :3730 Conformance behavior for operations is unclear | ||
+ | :3889 errors in standard extensionDefinitions | ||
+ | |||
+ | *MnM Block vote: | ||
+ | :5871 Time/DateTime DataType RegExes Don't Match Descriptions | ||
+ | :5819 Rename ElementDefinition.synonym to alias or otherName | ||
+ | :5812 Rename ElementDefinition.binding.reference[x] to codes[x] | ||
+ | :5533 Should Given and Family name fields of HumanName be strings, not IEnumerable<string>? | ||
+ | :5500 Jan 2015 Ballot Comment #437 (remove erroneous narrative range flag) | ||
+ | :5499 Jan 2015 Ballot Comment #436 (effect of no content in attachment not persuasive) | ||
+ | :5239 Jan 2015 Ballot Comment #116 (map data absent reasons to nullFlavors) | ||
+ | :3691 Context conduction in contained is dangerous (clarification of text) | ||
+ | |||
+ | *Publishing | ||
+ | :5898 Validation tooling isn't checking value set alignment of profiles | ||
+ | :5874 In hierarchy view, show Extension type, not Extension | ||
+ | :5805 OperationOutput should be removed from ValueSet based Validate operation | ||
+ | :5792 generate expansions with code system version populated in the build tool | ||
+ | :5664 Identifier use cardinality should be 1..1 | ||
+ | :5513 Ambiguous operation $validate | ||
+ | :5449 Jan 2015 Ballot Comment #355 - better structure for profile lists | ||
+ | :5373 Jan 2015 Ballot Comment #260 - make consent obvious | ||
+ | :5218 Jan 2015 Ballot Comment #95 - make TOC more obvious | ||
+ | :5182 Jan 2015 Ballot Comment #56 - resource list structure (**not persuasive**) | ||
+ | :3964 No section numbers within profiles | ||
+ | :3872 Need a way to profile a profile | ||
+ | :3831 Add reminders for nesting levels in table views | ||
+ | :3810 Resource package/profile list should link directly to profile if only one is defined for unique id | ||
+ | :3791 create examples tab for extensions | ||
+ | :3534 Need a formal support mechanism for i18n and l10n of schemas and schematrons | ||
+ | :3512 in the documents section point to the example | ||
+ | |||
+ | *''Excluded the following'' | ||
+ | :3856: Please document the preferred methods for extending operations for local use by a specific implementation | ||
+ | :2840 Address can't differentiate physical and postal | ||
+ | :3966 Summary view in profiles is inappropriate | ||
+ | :3868 Enhance the snapshot view | ||
+ | |||
+ | Motion: Approve the FHIR Core, MnM, Publishing & Additional FHIR Core with exclusions emailed by Lloyd | ||
+ | :Austin/Gordy 5-0-0 | ||
+ | |||
+ | ===5353 Add "type" to Identifier=== | ||
+ | Will add "code" to the Identifier type as 0..1 CodeableConcept. Binding as "extensible" (must use one of the approved codes if one applies - for interoperability, can supplement with local translations or with additional codes if none of the HL7 codes applies). Will add usage notes that the code is not a substitute for "system" and that codes should not be defined that are 1..1 with system. Will add the above guidance on what codes will be accepted into the HL7-maintained value set as part of the definition. | ||
+ | :Austin/Gordy 5-0-0 | ||
+ | |||
+ | ===5654 Integers for negative numbers=== | ||
+ | Will retain integer and define unsignedInteger and positiveInteger constraints and will update existing resources to reference constrained types as appropriate, consulting with WGs when the appropriate constraint is unclear. | ||
+ | :Austin/Gordy 5-0-0 | ||
+ | |||
+ | ===Timing proposals=== | ||
+ | *3841 Revise Timing Structure | ||
+ | *5347 Add range for frequency | ||
+ | *5673 With Meals | ||
+ | |||
+ | Will change "repeat" to contain the following properties: | ||
+ | :bounds : Period 0..1 - outer bounds for start and end of the timing schedule | ||
+ | :count : integer 0..1 - a number of times to do this within the bounds | ||
+ | :duration : decimal 0..1 - how long this thing happens for when it happens | ||
+ | :durationUnits : code 0..1 - UCUM units for duration | ||
+ | :frequency : integer 0..1 - number of times to repeat the action within the specified period or period range | ||
+ | :frequencyMax : integer 0..1 - if present, indicates that the frequency is a range - so repeat between [frequency] and [frequencyMax] times within the period or period range | ||
+ | :period : decimal 0..1 - Indicates the duration of time over which repetitions are to occur. E.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period | ||
+ | :periodMax : decimal 0..1 - If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days | ||
+ | :periodUnits : code 0..1 - UCUM units for period + periodMax | ||
+ | :when : code 0..1 - a real world event that the occurrence of the event should be tied to. | ||
+ | |||
+ | Will retain "event" as a repeating dateTime (rather than Period - can get the duration from Repeat), but indicate that it is distinct from "repeat" and that both can be present. The "event" represents the explicit scheduling of the information in repeat. At least one of repeat or event should be present (warning - allows for extensions). | ||
+ | |||
+ | Will add a number of examples - starting with the ones Gordy provided | ||
− | + | 2015/03/19 MnM FHIR call Gordy/Daniel 5-0-0 | |
− | |||
− | |||
− | |||
− | + | ===Tracker item 5664=== | |
+ | 2015/03/19 FHIR MnM call Austin/Daniel 5-0-0 | ||
==Adjournment== | ==Adjournment== | ||
+ | 2:05pm |
Latest revision as of 19:17, 21 March 2015
M&M Conference Call 1:00PM Eastern Time (Date above)
Agenda
- Approve Minutes Prior Meeting on 03/12
Attendees
- Lloyd McKenzie (chair)
- Austin Kreisler
- Gordon Raup
- Chad Armstrong
- Daniel Lanphear
- Mark Kramer
Minutes
Approved minutes of 03/12
- Austin/Daniel 5-0-0
Block votes
- FHIR Core block vote:
- 5866: Split $meta-change into $add-meta and $delete-meta
- 5818: DataElement should use ElementDefinition
- 3903: Conformance searchParam are not 'additional'
- 3889: errors in standard extensionDefinitions
- 3858: Need to define behavior around ignoring updates
- 3830: Clarify effect of deletion on resource history
- 3821: Add code system manifest to ValueSet expansion
- 3761: Clarification of how to implement search on boolean fields (e.g. Patient.active)
- 3744: Create operation - should the effects of idempotence be described?
- 3740: The list of FHIR datatypes should be explicit about "element" and derived types
- 3694: ConceptMap.name should be 0..1
- 3692: Remove type idref
- 3664: Profile definition for "Any"
- 3591: Versionless updates should be permitted
- 3522: Extensibility page has incorrect example for modifier, and has xml-specific language
- 3516: Document what the 'lock' icon means in the xml comments
- 3504: Can extensions have values and sub-extensions?
- 3468: Tool extensions should be moved to resource-specific profiles
- 3235: Example name guidance
- 3342: contained resources overrepresented in examples
- 3807: Should add rationale to Invariant
- 3802: Specify what it means for a search parameter to matches a complex datatype
- 3773: Other needs to be renamed
- 3650: Clarify format of Profile.extensionDefn.context
- 3381: Objective-C Reference Implementation from Download page is broken
- 3835: Rename keyword "metadata" to "_metadata" (Propose to reject this)
- 3859: add clarifying text for Profile.x.element.type.profile (Propose to reject this - something similar in intent but different in details done as part of StructureDefinition change)
- 3860: REST Search syntax clarification
- 3873: Explicitly specify resource/element types throughout? (Note: this one won't be applied to later, it's a massive change, but it's definitely needed to be done)
- 3880: extension content model example change request
- 3890: consistent use of 'any' for extensionDefinitions
- 3901: ;in should be :not?
- 3906: Broken Links
- 3910: Separate the updateCreate Resource property into an updat and create values
- 3924: Add clarification on case sensitivity in search vs validation
- 3928: Make parameter types hyperlinks
- 3933: Parameter resource does not support parts that are resources
- 5219: Fix cardinality of Narrative structure
- 5236: fix typo in example
- 5242: Jan 2015 Ballot Comment #119 (refer to extension registry)
- 5289: Jan 2015 Ballot Comment #168 - improve documentation about group and list
- 5311: Jan 2015 Ballot Comment #190 (move narrative about profiles)
- 5513: Ambiguous operation $validate
- 5601: Add an explicit specification of the resource identifier
- 5605: Unclear how to know what filters a given system supports for a given code system
- 5780: FHIR id definition is inconsistent
- 5796: Prohibit versionId and lastUpdated for contained resources
- 5816: Update documentation about extensions in compartments
- 5837: Additional issue types for warnings
- 5851: "Binding can only be present for coded elements" needs to be updated on DataElement
- 3730 Conformance behavior for operations is unclear
- 3889 errors in standard extensionDefinitions
- MnM Block vote:
- 5871 Time/DateTime DataType RegExes Don't Match Descriptions
- 5819 Rename ElementDefinition.synonym to alias or otherName
- 5812 Rename ElementDefinition.binding.reference[x] to codes[x]
- 5533 Should Given and Family name fields of HumanName be strings, not IEnumerable<string>?
- 5500 Jan 2015 Ballot Comment #437 (remove erroneous narrative range flag)
- 5499 Jan 2015 Ballot Comment #436 (effect of no content in attachment not persuasive)
- 5239 Jan 2015 Ballot Comment #116 (map data absent reasons to nullFlavors)
- 3691 Context conduction in contained is dangerous (clarification of text)
- Publishing
- 5898 Validation tooling isn't checking value set alignment of profiles
- 5874 In hierarchy view, show Extension type, not Extension
- 5805 OperationOutput should be removed from ValueSet based Validate operation
- 5792 generate expansions with code system version populated in the build tool
- 5664 Identifier use cardinality should be 1..1
- 5513 Ambiguous operation $validate
- 5449 Jan 2015 Ballot Comment #355 - better structure for profile lists
- 5373 Jan 2015 Ballot Comment #260 - make consent obvious
- 5218 Jan 2015 Ballot Comment #95 - make TOC more obvious
- 5182 Jan 2015 Ballot Comment #56 - resource list structure (**not persuasive**)
- 3964 No section numbers within profiles
- 3872 Need a way to profile a profile
- 3831 Add reminders for nesting levels in table views
- 3810 Resource package/profile list should link directly to profile if only one is defined for unique id
- 3791 create examples tab for extensions
- 3534 Need a formal support mechanism for i18n and l10n of schemas and schematrons
- 3512 in the documents section point to the example
- Excluded the following
- 3856: Please document the preferred methods for extending operations for local use by a specific implementation
- 2840 Address can't differentiate physical and postal
- 3966 Summary view in profiles is inappropriate
- 3868 Enhance the snapshot view
Motion: Approve the FHIR Core, MnM, Publishing & Additional FHIR Core with exclusions emailed by Lloyd
- Austin/Gordy 5-0-0
5353 Add "type" to Identifier
Will add "code" to the Identifier type as 0..1 CodeableConcept. Binding as "extensible" (must use one of the approved codes if one applies - for interoperability, can supplement with local translations or with additional codes if none of the HL7 codes applies). Will add usage notes that the code is not a substitute for "system" and that codes should not be defined that are 1..1 with system. Will add the above guidance on what codes will be accepted into the HL7-maintained value set as part of the definition.
- Austin/Gordy 5-0-0
5654 Integers for negative numbers
Will retain integer and define unsignedInteger and positiveInteger constraints and will update existing resources to reference constrained types as appropriate, consulting with WGs when the appropriate constraint is unclear.
- Austin/Gordy 5-0-0
Timing proposals
- 3841 Revise Timing Structure
- 5347 Add range for frequency
- 5673 With Meals
Will change "repeat" to contain the following properties:
- bounds : Period 0..1 - outer bounds for start and end of the timing schedule
- count : integer 0..1 - a number of times to do this within the bounds
- duration : decimal 0..1 - how long this thing happens for when it happens
- durationUnits : code 0..1 - UCUM units for duration
- frequency : integer 0..1 - number of times to repeat the action within the specified period or period range
- frequencyMax : integer 0..1 - if present, indicates that the frequency is a range - so repeat between [frequency] and [frequencyMax] times within the period or period range
- period : decimal 0..1 - Indicates the duration of time over which repetitions are to occur. E.g. to express "3 times per day", 3 would be the frequency and "1 day" would be the period
- periodMax : decimal 0..1 - If present, indicates that the period is a range from [period] to [periodMax], allowing expressing concepts such as "do this once every 3-5 days
- periodUnits : code 0..1 - UCUM units for period + periodMax
- when : code 0..1 - a real world event that the occurrence of the event should be tied to.
Will retain "event" as a repeating dateTime (rather than Period - can get the duration from Repeat), but indicate that it is distinct from "repeat" and that both can be present. The "event" represents the explicit scheduling of the information in repeat. At least one of repeat or event should be present (warning - allows for extensions).
Will add a number of examples - starting with the ones Gordy provided
2015/03/19 MnM FHIR call Gordy/Daniel 5-0-0
Tracker item 5664
2015/03/19 FHIR MnM call Austin/Daniel 5-0-0
Adjournment
2:05pm