Here is the text we could read:
Approved, SCAO
STATE OF MICHIGAN
JUDICIAL CIRCUIT - FAMILY DIVISION
COUNTY
MOTION OBJECTING TO
DNA IDENTIFICATION PROFILE OR
BLOOD / TISSUE TYPING SUMMARY REPORT
FILE NO.
In the matter of
Full name of child
1. On
Date
of the newborn child named above.
, a surrendered newborn child
, I received a DNA identification profile or summary report regarding my parentage
2. My specific objections to the DNA identification profiling and or the summary report are:
Foundation testimony is needed for admission of the DNA identification profile or summary report because:
Other proof of authenticity or accuracy is needed for admission of the DNA identification profile or summary report because:
(specify reasons)
3. I REQUEST the court to conduct a hearing to determine the admissibility of the DNA identification profile or summary report.
I declare that this motion has been examined by me and that its contents are true to the best of my information, knowledge, and belief.
Attorney signature
Signature of petitioner
Attorney name (type or print)
Bar no.
Name (type or print)
Date
Address
Address
City, state, zip
Telephone no.
City, state, zip
Telephone no.
Do not write below this line - For court use only
MCL 712.11, MCL 722.716
CCFD 05 (9/11) MOTION OBJECTING TO DNA IDENTIFICATION PROFILE OR BLOOD / TISSUE TYPING SUMMARY REPORT
Motion Objecting to DNA Identification Profile or Blood/Tissue Typing Summary Report
This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Michigan state courts.
To learn more about the project, check out our about page.
Downloads: You can download both the original form (last checked 2023-03)
and the machine-processed form with normalized data fields.
About This Form:
Use our Rate My PDF tool to learn more.
Go beyond the above insights and learn more about this or any pdf form at
RateMyPDF.com, includes: counts of difficult words used,
passive voice decetion, and suggestions for how to make the form more usable.
Identified Data Fields:
We have done our best to automaticly identify and name form fields according to our naming conventions.
When possible, we've used names tied to our question library. See e.g., user1_name.
If we think we've found a match to a question in our library, it is highlighted in green. Novel names are auto generated. So, you will probably need to edit some of them if you're trying to stick to the convention.
Here are the fields we could identify.
cir was cir (0.61 conf)county was county (0.39 conf)docket_number was filenumber (1.00 conf)users1_name was name (1.00 conf)box was box2a (0.35 conf)box_b was box2b (0.35 conf)signature_date__1 was date2 (1.00 conf)aname was aname (0.35 conf)abar was abar (0.35 conf)aaddress was aaddress (0.35 conf)citystatezip was citystatezip (0.35 conf)atelno was atelno (0.35 conf)pname was pname (0.35 conf)paddress was paddress (0.35 conf)pcitystatezip was pcitystatezip (0.35 conf)ptelno was ptelno (0.35 conf)signature_date__2 was date (1.00 conf)text was text1 (0.35 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
Suggested Screen 1:
Suggested Screen 2:
Suggested Screen 3:
Suggested Screen 4:
anameabaraaddresscitystatezipatelnopnamepaddresspcitystatezipptelno
Suggested Screen 5:
Create an Interactive Version of this Form:
The Weaver creates a draft guided interview from a template form, like the one provided here.
To learn more, read "Weaving" your form into a draft interview.