Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdht-dev] Bug in MDHT?

Hi Sean,

 

Thanks for the clarification. On top of the consistency issue, the “If section/@nullFlavor is not present,” text shouldn’t appear at all if @nullFlavor has been explicitly prohibited.

 

Thanks

David

 

From: mdht-dev-bounces@xxxxxxxxxxx [mailto:mdht-dev-bounces@xxxxxxxxxxx] On Behalf Of Sean Muir
Sent: Wednesday, 25 May 2016 9:17 PM
To: mdht developer discussions <mdht-dev@xxxxxxxxxxx>
Subject: Re: [mdht-dev] Bug in MDHT?

 

Morning 

This feature was explicitly added to support the ability to satisfy “Section Requirements” for a clinical document when as a implementer you did not have any information or data to supply;  For instance - Continuity of Care requires Medication Section - in order to satisfy the requirement, implementers created null flavor entries in the section; the null flavor at the section is meant to turn off any requirements for entries (title and text are still required)

 

This was a quickly implemented solution to initial certification efforts and probable should be revisited through the struc docs group (this is a us realm as far as i know)

 

In the mean time - we should probable fix the inline issue to be consistent

 

Thanks

 

Sean

 

On May 23, 2016, at 9:24 PM, David Cai <David.Cai@xxxxxxxxxxxx> wrote:



Hi All,

 

We have identified a potential bug in DITA generation in MDHT.

 

In a section, where an entry is typed to a template that is defined externally, then the following text prefaces the parent constraint: “If section/@nullFlavor is not present,” .

 

Issues:

1.       This text appears only where a CDA class is typed to an externally defined template - the text does not appear when typed to an internally defined template or an inline class. The wording of this text infers additional normative content and is therefore problematic that it should be included or excluded for reasons based on reuse practices instead of normative meaning.

2.       The above text is included even when @nullFlavor has been explicitly prohibited for that section. The inclusion of the text is misleading as it implies that @nullFlavor is allowed for that section.

3.       A section with a nullFlavor does not have to mean that it cannot have an entry

 

Can we not include this text if it is a bug?

 

Thanks

David Cai
Business Analyst

Strategy, Architecture & Informatics Group
nehta - National E-Health Transition Authority 
Office address
Phone: (07) 3023 8598 
Fax: (07) 3023 8466
Email: david.cai@xxxxxxxxxxxx 
Web: www.nehta.gov.au

 



The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files. _______________________________________________
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

 



The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files.

Back to the top