This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "PertinentInformationism"

From HL7Wiki
Jump to navigation Jump to search
 
Line 5: Line 5:
  
 
The "transformation" of a legacy business process (and a single legacy information representation) should take place at the business process level and its requirements, and not at the information representation level. The business process may be supported by more than one models in HL7 version 3.
 
The "transformation" of a legacy business process (and a single legacy information representation) should take place at the business process level and its requirements, and not at the information representation level. The business process may be supported by more than one models in HL7 version 3.
 +
 +
:If one has a business-process reason for squeezing a specific set of information into a single static model, then one should seriously consider whether the use of a [[CDA]] document is more appropriate than a message. [[User:Rene spronk|Rene spronk]] 09:20, 1 September 2006 (CDT)
  
 
==Symptoms==
 
==Symptoms==

Revision as of 14:20, 1 September 2006

PertinentInformationism is a syndrome, the main symptom of which is the use of a significant number of pertinentInformation act relationships.

Cause

When developing/localizing models, pertinent informationism is a syndrome caused by neglect of business processes in information models. The focus is on (legacy-) information representation and not on the underlying business processes.

The "transformation" of a legacy business process (and a single legacy information representation) should take place at the business process level and its requirements, and not at the information representation level. The business process may be supported by more than one models in HL7 version 3.

If one has a business-process reason for squeezing a specific set of information into a single static model, then one should seriously consider whether the use of a CDA document is more appropriate than a message. Rene spronk 09:20, 1 September 2006 (CDT)

Symptoms

  • The use of large number of pertinentInformation act relationships.
  • It often is accompanied by cravings for de-novo attributes, because the relationship of the information to the business processes is neglected, and hence it looks like it's all just some new unrelated attributes.
  • "Complicated data structure" is another alarm-word for this same disease. It's the denial of looking at the processes and wanting to shoehorn a foreign preset model into the HL7 world (or any other model foreign to those preset ideas of those "information structures".)