Ah ok.
I guess the answer lies with what you are looking to do with your profile. If you have followed the instructions to add extensions to your own custom type, and you use that type on a server, you'll actually automatically get a profile generated. You need to give your custom type a profile ID by setting the ID in your @ResourceDef annotation, e.g.
@ResourceDef(name="Patient", id="mypatient")
Once you do this, the server automatically exports a profile at the address:
http://[base]/Profile/mypatient
If you're looking to constrain, things are a little bit less clear. We haven't implemented the ability to constrain using profiles yet, mostly because it hasn't been clear what people want to do. It seems like the something that would be great to have would be the ability for you to define a constrained profile using the "Forge" tool produced by Furore and then we could have HAPI's code generator turn that into a custom type for you that enforces all of your constraints at compile time. If that sounds like something that would suit your requirements, maybe we could collaborate on getting that going?