Re: [mdht-dev] Validation Properties

[Dave Carlson <dcarlson@xxxxxxxxxxxxxxx>]

Sean,

Yes, the two types of validation were developed at different times.  The code shown, part of the CDA profile, was done in initial design ~5 years ago.  The Validation profile and its stereotypes was added later by Christian in order to allow validating the UML model itself.

The CDA profile is only loaded once into the shared ResourceSet.  The getCDAProfile() method simply iterates through already loaded resources to find the CDA profile package, so it should be reasonably efficient.

Thank you,

  Dave Carlson, Ph.D.

  mobile: 406-253-3055

  email: dcarlson@xxxxxxxxxxxxxxx

  Clinical Cloud Solutions LLC, healthcare on HL7 FHIR

On Tue, Nov 10, 2015 at 3:05 PM, Sean Muir <sean.w.muir@xxxxxxxxx> wrote:

Dave -

I was updating the validation stereotype to add to additional attributes

I noticed in the code set we have code such as to populate severities - 

Enumeration severityKind = null;

 

Profile cdaProfile = CDAProfileUtil.getCDAProfile(modelElement.eResource().getResourceSet());

if (cdaProfile != null) {

severityKind = (Enumeration) cdaProfile.getOwnedType(ICDAProfileConstants.SEVERITY_KIND);

}

Two questions - How come we do not leverage the Validation eclass (assume this was a timing issue with static profiles)

second - we end up loading the profile numerous times - based on the model element - this seems inefficient and was wondering if there was a particular reason

Thanks

Sean

_______________________________________________
mdht-dev mailing list
mdht-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdht-dev