OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

tgf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [bcm] Re: Statement of eDevice Work Effort



Personally I think CAM is too far down in the technical weeds for the TGF but maybe the BCM has a place in the semantic layer of the TGF rather than the BMF layer.  It needs a closer examination and more thought so I’ll add it to our Wishes List for the next version of the TGF and we can take a view when we get round to working up that version.





From: tGov: Hans A. Kielland Aanesen [mailto:hans@eprforum.no]
Sent: 27 November 2012 16:34
To: John Borras
Cc: Carl Mattocks; David RR Webber
Subject: Fwd: [bcm] Re: Statement of eDevice Work Effort


Hi John,
Regarding strengthening the public Frontline services ( interaction of service management and deviation in environment and body sensors), we should may be introduce for OASIS TGF and its BMF(Business Management Framework) the OASIS CAM and OASIS BCM work ?


-------- Opprinnelig melding --------


[bcm] Re: Statement of eDevice Work Effort


Mon, 26 Nov 2012 15:52:29 -0500


carl mattocks <carlmattocks@gmail.com>


bcm@lists.oasis-open.org, paul alagna <PJAlagna@gmail.com>

BCM Folk:


Please review latest version of OASIS Business-Centric Methodology (BCM) Technical Committee Statement of eDevice Work Effort

The BCM TC recognizes that concurrent evolution of cloud analytics and mobile medical device technology provides a great potential for collaborative informatics and streamlined data sharing. To provide guidance the TC eDevice work effort is focused on defining how BCM Template & Rules will provide business managers with a set of clearly defined methods for medical device & cloud analytic interchange scenarios.

Conformant with our charter the BCM TC will build upon existing bodies of work and individual member insights. Such as, eDevice semantics that reference elements of the (i)Food and Drug Administration (FDA) Unique Device Identification (UDI) and (ii) EPR-Forum Norwegian Health Care Templates derived from ANSI/CEA-721.

(1) BCM Templates are pre-constructed components that enable data interchange outcome scenarios that conform to and are illustrative of the BCM use of Template constrained linking and switching. For example:

·  eDevice Template linking and switching for Citizen Service management

·  eDevice Template linking and switching for Wellness monitoring management

(2) BCM Collaborative relationships form the information architecture underpinning for the Templates and provide understanding of component actuation. For example:

  • eDevice Elements are ontological concepts used to explain the contractual usage for Template information elements and data archetypes (computable domain _expression_) of a specific interchange 
  • eDevice Method rules identify the semantic and syntactic sequencing that forms valid Template statements implementable in a common application language method.

(3) BCM Template Connections validate component interoperability across existing frameworks and methodologies. For example:

  • Wellness eDevice ontological concepts are taxonomically aligned with Unique Device Identification (UDI) & the ANSI/CEA-721 standard
  • Wellness eDevice rules build on (xpath form) OASIS CAM specification rules and reference state management of ANSI/CEA-721  CAL (Generic Common Application Language) for decision operations upon Values(IV) in Objects (eDeviceOB) 



Carl Mattocks

President Berkeley Underwater Search & Rescue
Principal Wellness Intelligence Institute

Chair OASIS Business Centric Methodology TC
Cell (usa) (732) 497-CARL {2275}




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]