11073 Device Profile Tooling September Michael Faughn Prometheus Computing LLC

Transcription

1 11073 Device Profile Tooling September 2016 Michael Faughn Prometheus Computing LLC

2 DIM UML development Initial UML model programmatically derived from :2004 in early 2012 Work on applications begun FY 2013 Manual revisions performed Supporting models integrated IEEE11073:10101 Nomenclature (RTMMS) IEEE11073:20101 (ASN.1 Simple Types) Device Profiles Metamodel (represents UML in web applications) Printed Standard Conformance Statements (work in progress)

3 DIM UML development Supporting models integrated IEEE11073:20601 Personal Health Devices IEEE11073:10101 Nomenclature (RTMMS) IEEE11073:20101 (ASN.1 Simple Types) Device Profiles - Needs Revision Metamodel (represents UML in web applications) Printed Standard Conformance Statements (work in progress)

4 DIM Classes This shows only the classes defined by the standard. There are ~350 classifiers total in the DIM model. The Device Profiling application relies on several other supporting models (MetaInformation, Nomenclature, DeviceProfile, etc.) that interact with the DIM model. The Device Profiling application implements ~440 classes specific to the application.

5 The Model is the Standard Why? Computable Artifacts programmatically derived from a common source help to ensure harmonization. Printed Standard Software tools (Device Profiling, Validation,...) XML Schema Conformance Statements

6 UML to Artifacts: Challenges UML (or UML tools) has trouble expressing some constructs in a convenient way Class instance variables BNF (i.e. ASN.1) BIT STRING Each UML element type used has to be implemented for each builder plugin that produces an artifact. Lots of work the first time you do it and every time you build a new plugin. Keep the standard pure vs. supporting the functionality that artifacts require.

7 Published PHD UML Should Metric to PM-Segment be one-to-one? It is many-to-many in

8 PHD Classes

9 Programmatically Derived / Generated From UML Device Profile Editor web application ~ 3,000 lines of in-memory code per classifier XML Schema ASN.1 Relational database schema Rich Ruby API for interacting with DIM objects.docx JSON meta-information

10 Workflow (Simplified)

11 Device Profile Editor Existing Capabilities 1/3 Assemble DIM objects into device profile containment trees. Composition constrained by the standard View the containment tree Allow creation of Normative ( xx) and User Defined device profiles. Use any device profile as a template for a new device profile via cloning Entire containment tree must be cloned Items in blue applicable to profiles for both 11073:10201 and 11073: Otherwise the item applies only to 11073:10201 profiles.

12 Device Profile Editor Existing Capabilities 2/3 Allow user to view metadata about DIM classes and attributes (i.e. what is found in the paper standard) Associate device profile elements with terms from RTMMS. Fetch new and updated terms from RTMMS. Items in blue applicable to profiles for both 11073:10201 and 11073: Otherwise the item applies only to 11073:10201 profiles.

13 Device Profile Editor Existing Capabilities 3/3 Summary XML (Rosetta Containment Hierarchy) representation of a device profile Detailed HTML report of containment and terminology Comprehensive representation of Device Profile in XML Comprehensive representation of Device Profile in JSON (same info as XML, different format). Items in blue applicable to profiles for both 11073:10201 and 11073: Otherwise the item applies only to 11073:10201 profiles.

14 Recent Features Create Device Profile by uploading XML Original file is stored Synchronized Rosetta Containment XML input and output formats for round-trip capable workflow HTML Rosetta report Significant UI/UX improvements Prevent user from doing harm Reduction of clutter and confusion Inclusion of UCUM units in application Visual cues providing conformance information Conformance messages on XML upload Support for the use of terms not found in RTMMS

15 Upload XML Device Profile

16 RCH XML Output Example

17 Newest Features Create Device Profile by uploading tables using dotted notation (TSV) Original file is will be stored Metric types must be guessed at in some cases PHD profiles gain support

18 FIXME with PHD picture!!!!!!!!!!!!!!!! Profile created by hand

19 REFID CF_CODE10 UOM_MDC UOM_UCUM CF_UCODE10 Enum_Values MDCX_DIALYSIS_MACHINE_MDS. MDCX_DIALYSIS_MACHINE_VMD.. MDCX_DIALY_CONFIG_INFO_CHAN... MDCX_DIALY_MACH_TIME... MDCX_DIALY_MACH_MODEL... MDCX_DIALY_MACH_SERIAL_NO... MDCX_DIALY_MACH_VERSION. MDCX_DIALYZER_VMD.. MDCX_DIALYZER_FILTER_CHAN... MDCX_DIALY_FILTER_MGR_AND_UNIQUE_ID... MDCX_DIALY_FILTER_TRANSMEMBRANE_PRESS MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_MIN_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_MAX_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_MIN_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_MAX_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS_MIN_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS_MAX_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_BLOOD MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS_BLOOD MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_LO_NON_ALM MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_INLET_PRESS_HI_NON_ALM MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS_LO_NON_ALM_SETTING MDC_DIM_MMHG mm[hg] MDCX_DIALY_FILTER_OUTLET_PRESS_HI_NON_ALM_SETTING MDC_DIM_MMHG mm[hg]

20 Containment Tree and Object Node Profile created from TSV upload

21 Problem! Performance / Application Responsiveness Uploading a large profile via XML or TSV can take a really long time minutes Proxy server times out and it appears that the application has completely failed (even though it is still processing and creating the profile) Deleting a profile can take almost as long

22 Near Term Goals PHD profile functionality working as well as PCD profiles Address the performance issues Freeze features

23 Next Steps (after the freeze) Generate camera ready IEEE standard in MS Word Redesign application for reusable profiles Resolve critical issues on Revisions & Comments

24 Application Redesign Device components (e.g. VMDs, Channels) become reusable and shareable across multiple containing profiles A change to one component will propagate to all occurrences Choices (any of, one of) within normative profiles Further attention to performance issues XML Schemas for Profiles?

25 Re pla ce wi th cu sto m GU I Workflow (Simplified)

26 More Goals Finish implementation of r/w permissions in web application Improve integration with RTMMS Report new terms, etc. Comprehensive audit of updated DIM model / application with respect to 11073: Easier access to metadata and information from the DIM standard for device profile users

27 More Goals (cont.) User documentation / help for device profiling application Deploy to NIST server Release Device Profiling app for general use Conformance statements from the profile editor

28 dim.prometheuscomputing.com user: dim password: 11073