Since any AS can be linked to a specific LOINC test, this relation should be displayed/modified somewhere in-site. Therefore, a field 'LOINC Test' with a searchable textbox linked to registered "LOINC Tests" must be added inside the AS creation/edit form. Manual creation of LOINC tests (or Term classes, etc.) has no sense imo, so Bika Health should have, by default, all LOINC tests registered in the system, also if no setup-data import is done. The same applies for Analysis categories and AR Templates/Profiles.
Not sure, but in most cases I suppose the user will set the same AS name and keyword to newly created ASes as those from the 'linked' LOINC test. Why don't to use the 'LOINC Test' field described above to automatically set the name and keyword of the AS to be created? IMO, it will make the creation easier and will help to avoid missunderstandings between AS keywords and LOINC tests codes.
Regards to the automatic creation of 'Analysis Service Categories' due to the creation of new ASes linked to a LOINC: I was thinking about the registry form (HEALTH-140), in which the tests must be displayed inside panels. These panels should be displayed/hide depending the 'AR Template' or 'AS Category' selected. As far as Bika's Categories have to be linked again with LOINC Term Classes, I think the best way is to follow the same procedure descibed above for AS. That will help to maintain the integrity and consistency of all the system. LOINC's Term Classes must be registered in the system by default again, so I think that the automatic creation of the missing Bika's category linked to the LOINC Term class to which the new AS is associated (by using the linked LOINC Test info), might speed up the process, as well as, ensure the integrity and consistency again.
Thinking loud: another option could be to create all LOINC Term classes as Analysis Categories and set all of them disabled by default during the site creation.