IHE Patient Care Device Technical Framework

specializations defined below:Virtual Medical Device (VMD) AttributesAttribute Description Term Code DataType 16TypeVMD-StatusVMD-ModelProduction-SpecificationPositionLocaleGeneralcategory ofthe VMD(e.g., infusionpump)VMD’s basicoperationalstatusManufacturer& Model labelstringsList of serialnumbers andother itemssuch asGMDN codePhysical“slot” that theVMD isplugged intoStructuredefining thedevice’scountry,language andcharactersetting.MDC_ATTR_ID_TYPE(1::2351)MDC_ATTR_VMD_STAT(1::2466)MDC_ATTR_ID_MODEL(1::2344)MDC_ATTR_ID_PROD_SPECN(1::2349)MDC_ATTR_ID_POSN(1::2348)MDC_ATTR_LOCALE(1::2600)TYPETEXT 17SystemModelList ofProdSpecEntryUInt16 3LocaleValuesFor example,MDC_DEV_SYS_PT_VENT_VMD(1::4466)“vmd-off”, “vmd-not-ready”, “vmdstandby”,“vmd-transduc-discon”,“vmd-hw-discon”manufacturer=”Philips”model=”IntelliVue MP70”serial-number=”XYZ12345”sw-revision=”03.02.01”Same as MDS above.D.7 Channel semanticsChannels provide aggregation for closely related parameters. For devices that contain“channels” (e.g., ECG channels or infusion pump fluid channels), these definitionsprovide a means for differentiating parameters with identical term codes (e.g., fluidsource channel rate or volume infused) but contained in different channels. The attributes16 Data types are further defined in section 3.2.6.3D.4 Basic data type specifications.17 For the purposes of this technical framework, this data type which is VMDStatus, an enumerated set ofbit flags, is defined as a set of string values; multiple of these may be active at the same time.