ANSI Anti-Trust Policy:
Professional Associations, such as HL7, which bring together competing entities are subject to strict scrutiny under applicable antitrust laws. HL7 recognizes that the antitrust laws were enacted to promote fairness in competition and, as such, supports laws against monopoly and restraints of trade and their enforcement. Each individual participating in HL7 meetings and conferences, regardless of venue, is responsible for knowing the contents of and adhering to the HL7 Antitrust Policy as stated in §05.01 of the Governance and Operations Manual (GOM).
Meeting Details
Date: January 10, 2022
Time: 2PM
Coordinates: Join Zoom meeting: https://zoom.us/j/5100467805 | Meeting ID: 510 046 7805 | +1 929-436-2866-US (New York)
Attendees
JD Nolen, Elliot Silver, Kathy Walsh, Yanick Gaudet, Marti Velezis, Maria Moen
Agenda
- JIRA Tickets - Backlog
- Next Meeting
LINKS TO JIRA - OO on FHIR DASHBOARDS
- OO on FHIR Dashboard - Includes all resources related to OO on FHIR
Meeting Notes
Administrative
- We will add OO R5 issues to the WGM Agenda (currently OO has 42 open Ballot comments)
JIRA Backlog
- FHIR-38633 - Target Awareness Element or Extension
- Propose that a complex extension be created
- awareness (0..*)
- subject (0..1) (e.g., Person/Patient, provider, relatedPerson)
- status (0..1) (codeableConcept)(e.g., uninformed, verified, unknown, read, completed) example binding
- dateTime (0..1)
- awareness (0..*) CodeableReference (Communication) does not seem to fit as well as the option above. This was suggested in the in Zulip.
- Will add this to the OO/PC Wednesday Q1. The ticket includes Observation and Condition resources
- awareness (0..*)
- Propose that a complex extension be created
- Question: What is the current status of the Device Association discussion
- Confluence: Device Association
- Need to determine if we need to expand this beyond devices
- Should we create a pattern for Associations that can be used by other product types (e.g., BDP, Nutrition, Medication and Devices)
- If we keep as DeviceAssociation resource
- DeviceAssociation will need to cover more usage types of scenarios
- Do we incorporate device operation elements (e.g., status, statusReason, operator, mode, cycle, duration)
- We need to determine what Resource Proposals need to be completed prior to the February cut off date (TBD)
- DeviceAssociation will need to cover more usage types of scenarios
- We will discuss with DEV group tomorrow 9AM EST and add topics to the WGM Agenda
- Need to determine if we need to expand this beyond devices
- Confluence: Device Association
- Meeting Adjourned at 3PM EST
Next Meeting: January 24, 2023
------end of meeting-----