Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

NOTE:  Copied from follow-up e-mail.

 

Participants:  Todd, Michael, John, Stefan

Discussion
  1. UDI @ PoCD Containment Review
    • Stefan reviewed the three alternatives for Device-to-DeviceComponent mapping to address composite UDI's
    • See attached,
  2. DoF PoCD Collaboration Tools
    • JR indicated that they were up and ready to go
    • TC & SK have yet to get logged on 
    • ACTION( TC & SK ) Work to get access, especially to use for the IG development
  3. DoF Wednesday Call
    • ACTION( TC ) Get wiki call pages in place - thought they were there already!
    • ACTION ( JR ) Ask Brian & Asim & Martin for any PHD-focused agenda items
    • Agenda
      • Review previous notes from 09/27 
      • PoCD NIB Review & Approval
      • UDI for Composed Devices (PoCD) [Karl]
      • PHD IG Update / Review
      • PoCD IG Outline Proposal
  4. PoCD Outline Template
    • ACTION( TC ) As Rutten if THIS was generated using Simplifier
    • IOW - How hard will it be to get to this
    • NOTE:  Get the basic shell in place ASAP so that we can start generating content
  5. PHD / PoCD Comparison 
    • MF reviewed a comparison spreadsheet HERE
    • This should prove very helpful when reviewing detailed mapping from the 11073-10201 DIM to FHIR Extensions and trying to ensure as much harmonization between PHD and PoCD as possible
  6. POCD Classes List
    • MF prepared and we reviewed a list of PoCD classes (see below)
    • From the discussion ... the IG should address:
      • Alert Package 
      • Control
      • PMStore / PMSegment - especially how represented in FHIR containment or other resource
      • RTSA - topic of other 
      • TimeSA (snippets) easily addressed
      • DistributionSA (e.g., for EEG) is also needed but a different beast :-) 
      • Battery may be particularly of use for "mobile" PoCD devices
      • Clock
      • EventLog is a challenge; high interest but TBD as to how to best represent content; perhaps consider using an Audit resource 
    • Out-of-scope (and should be so indicated somewhere are:
      • Archival Package
      • Communication Package
      • ExtendedServices Package
PoCD Classes
Alert::Alert
Alert::AlertMonitor
Alert::AlertStatus
Archival::Ancillary
Archival::MultiPatientArchive
Archival::PatientArchive
Archival::Physician
Archival::SessionArchive
Archival::SessionNotes
Archival::SessionTest
Communication::BCC
Communication::DCC
Communication::DeviceInterface
Communication::DeviceInterfaceMibElement
Communication::GeneralCommunicationStatisticsMibElement
Control::ActivateOperation
Control::LimitAlertOperation
Control::SCO
Control::SelectItemOperation
Control::SetRangeOperation
Control::SetStringOperation
Control::SetValueOperation
Control::ToggleFlagOperation
ExtendedServices::AlertScanner
ExtendedServices::ContextScanner
ExtendedServices::EpiCfgScanner
ExtendedServices::FastPeriCfgScanner
ExtendedServices::OperatingScanner
ExtendedServices::PeriCfgScanner
Medical::Channel
Medical::ComplexMetric
Medical::DistributionSampleArray
Medical::Enumeration
Medical::Numeric
Medical::PMSegment
Medical::PMStore
Medical::RealTimeSampleArray
Medical::SampleArray
Medical::TimeSampleArray
Medical::VMD
Patient::PatientDemographics
System::Battery
System::Clock
System::EventLog
System::MultipleBedMDS
System::SingleBedMDS