Difference between revisions of "PCD MEM 2009-05-05"

From IHE Wiki
Jump to navigation Jump to search
(New page: {{TOCright}} (MEM Profile Main Page) == Meeting Purpose == IHE PCD MEM Medical Equipment Management Discussion at Spring 2009 F2F (NIST, Was...)
 
m (l)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{TOCright}}
 
{{TOCright}}
  
[[PCD_Profile_Medical_Equipment_Management |(MEM Profile Main Page)]]
+
[[PCD Medical Equipment Management (MEM) - 2009 White Paper |(MEM Profile Main Page)]]
  
 
== Meeting Purpose ==
 
== Meeting Purpose ==
Line 7: Line 7:
  
 
== Proposed Agenda ==  
 
== Proposed Agenda ==  
:1  
+
:1 - Overview of MEM Status (New Directions Poster)
:2  
+
:2 - Detailed break-out of block diagrams
:3  
+
:3 - MEM Roadmap
:4
 
  
 
== Minutes ==
 
== Minutes ==
Line 16: Line 15:
 
=== Participants ===
 
=== Participants ===
  
:* See full F2F Minutes for reference list of attendance
+
:* [[PCD_PC%26TC_2009-05-04_to_08_F2F | See full F2F Minutes for reference list of attendance]]
  
 
=== Discussion ===  
 
=== Discussion ===  
Line 27: Line 26:
 
|-
 
|-
 
| align="center" | 1
 
| align="center" | 1
| '''Review '''
+
| '''Overview of MEM Status '''
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
'''Decisions/Issues:'''
+
'''
:*
+
The whitepaper is still under development.  Next steps
 +
:* Roadmap
 +
:* Clarify the use cases versus scenarios
 +
:* Clarify scope of the blocks
 +
'''<br>
 
'''Action(s):'''
 
'''Action(s):'''
 
|-
 
|-
 
| align="center" | 2
 
| align="center" | 2
| '''MEM Brainstorm'''
+
| '''Detailed break-out of block diagrams'''
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
'''Decisions/Issues:'''
+
'''
:* See Visio drawing of brainstorming session [ftp://ftp.ihe.net/Patient_Care_Devices/Profiles/MEM/WP/MEM-WPDetails.vsd ==here==]
+
: Patch Management
'''Action(s):'''
+
::* Rename to Software Management
 +
::* Pending software should be clarified
 +
:::* Downloaded and ready for install status
 +
:::* Authorized for installation status
 +
:::* Vendor supplied vs. OTS
 +
:::* Upgrades vs. Bug fixes
 +
::* Should be explicit that this is not a push mechanism, only a reporting mechanism
 +
::* Patch history should be another system not a function of this reporting
 +
::* There should be a method of site customized software level (i.e. a drug library in pumps)
 +
::* This could also be transformed to compatibility management for example wireless compatibility
 +
: Location Services
 +
::* Yes this is RTLS
 +
::* Not a protocol for location tracking but a method of exporting tracking information across the enterprise
 +
::* There was some work done on this several years back in HL7, need to investigate its status
 +
::* This would not be for location tracking (tag-type) companies but for interoperability vendors
 +
::* Only boundary alarms seems to have an obvious solution
 +
::* Also include in the scope a location query mechanism
 +
: Battery Management
 +
::* The topics included in the poster seem to represent the issues
 +
: Operational Status and Monitoring
 +
::* Define alerts versus alarms
 +
::* Include calibration check alarms
 +
'''<br>
 +
'''Action(s):
 +
Examine status of location services within HL7'''
 
|-
 
|-
 
| align="center" | 3
 
| align="center" | 3
| '''Use of existing IHE transactions'''
+
| '''MEM Roadmap'''
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
'''Decisions/Issues:'''
+
'''Decisions/Issues:
:* Was not discussed in depth.  A spreadsheet has been created to start mapping this [http://spreadsheets.google.com/ccc?key=rem-4YQ6tIhsWrJfBBr0b7A&inv=steve.merritt@bhs.org&t=6496636161240436288&guest ==here==] 
+
: Some of this could be solved using just an aperiodic PCD-01 message '''<br>
:* Everyone is encouraged to start adding to this spreadsheet.
+
'''Action(s):
'''Action(s):'''
+
: New Brief Profile Proposals for Cycle 5'''
|-
+
::* Battery management (leverage existing PCD-01)
| align="center" | 4
+
::* Location boundary alarms
| '''Open Discussion'''
+
: Other work items for Cycle 5
| '''Status/Discussion:'''
+
::* Nomenclature requirements (Data types, names, value sets)
'''Decisions/Issues:'''
 
:*  
 
'''Action(s):'''
 
:*  
 
 
|}
 
|}
  
Line 60: Line 83:
  
 
[[Patient Care Device | PCD Home]]
 
[[Patient Care Device | PCD Home]]
[[Category:PCD Meeting]]
+
[[Category:PCD Meeting Archive]]

Latest revision as of 11:37, 26 March 2012

(MEM Profile Main Page)

Meeting Purpose

IHE PCD MEM Medical Equipment Management Discussion at Spring 2009 F2F (NIST, Washington, DC)

Proposed Agenda

1 - Overview of MEM Status (New Directions Poster)
2 - Detailed break-out of block diagrams
3 - MEM Roadmap

Minutes

Participants

Discussion

Item Topic Discussion
1 Overview of MEM Status Status/Discussion:

The whitepaper is still under development. Next steps

  • Roadmap
  • Clarify the use cases versus scenarios
  • Clarify scope of the blocks


Action(s):

2 Detailed break-out of block diagrams Status/Discussion:

Patch Management
  • Rename to Software Management
  • Pending software should be clarified
  • Downloaded and ready for install status
  • Authorized for installation status
  • Vendor supplied vs. OTS
  • Upgrades vs. Bug fixes
  • Should be explicit that this is not a push mechanism, only a reporting mechanism
  • Patch history should be another system not a function of this reporting
  • There should be a method of site customized software level (i.e. a drug library in pumps)
  • This could also be transformed to compatibility management for example wireless compatibility
Location Services
  • Yes this is RTLS
  • Not a protocol for location tracking but a method of exporting tracking information across the enterprise
  • There was some work done on this several years back in HL7, need to investigate its status
  • This would not be for location tracking (tag-type) companies but for interoperability vendors
  • Only boundary alarms seems to have an obvious solution
  • Also include in the scope a location query mechanism
Battery Management
  • The topics included in the poster seem to represent the issues
Operational Status and Monitoring
  • Define alerts versus alarms
  • Include calibration check alarms


Action(s): Examine status of location services within HL7

3 MEM Roadmap Status/Discussion:

Decisions/Issues:

Some of this could be solved using just an aperiodic PCD-01 message

Action(s):

New Brief Profile Proposals for Cycle 5
  • Battery management (leverage existing PCD-01)
  • Location boundary alarms
Other work items for Cycle 5
  • Nomenclature requirements (Data types, names, value sets)

MEM Profile Main Page

PCD Home